Allen Bradley DH+.pdf - Logic, Inc.

Wonderware ®ABDHPLUS DAServer User’s GuideVersion 1.5Last Revision: 2/5/07Invensys Systems, Inc.

Contents 5Plug-ins............................................................................................ 86DAS Engine ..................................................................................... 87PLC Protocol Layer ......................................................................... 87Component Environments.................................................................... 87Index..................................................................89ABDHPLUS DAServer User’s Guide

6 ContentsABDHPLUS DAServer User’s Guide

Before You Begin 7Before You BeginAbout This BookThis user’s guide describes the user interface and functions of theWonderware ® ABDHPLUS DAServer . It also provides you with the stepby-stepprocedures on how to configure and use the ABDHPLUS DAServerafter it is installed.The ABDHPLUS user’s guide is organized in the following fashion:• Contents• Introduction: contains overview information about the ABDHPLUSDAServer and the environment in which it works.• Configuration: contains a detailed description of the user interfaceelements of this DAServer in addition to its functionality.• Item Names: describes the item naming conventions for targeted devices.• Troubleshooting: provides information about error messages, codes, andconditions displayed by the ABDHPLUS DAServer.• Reference: describes DAServer architecture in general.• IndexYou can view this document on-line or you can print it, in part or whole, byusing the Adobe Acrobat Reader’s print facility. To view this documentproperly, you must use version 4.0 of the Acrobat Reader.ABDHPLUS DAServer User’s Guide

Introduction 9CHAPTER 1IntroductionThis chapter provides an overview of the Wonderware ABDHPLUSDAServer, including application and bus-level communications protocols,item naming conventions, and the DAServer features.Contents• Overview• Communications Protocols• Accessing Items via the DAServer• Features• Demo ModeOverviewThe Wonderware ® ABDHPLUS DAServer, as part of the Rockwell_DASpak,is the next-generation server for the current Wonderware Allen-Bradley 1784-KT and SST 5136-SD I/O Servers.This DAServer is a Microsoft ® Windows ® application program designed toprovide direct and indirect connectivity to the Allen-Bradley families of PLC-5and SLC 500 controllers. The DAServer acts as a communications protocolserver and allows other Windows application programs access to data in theAllen-Bradley PLC-5 and SLC 500 PLCs (also referred to as devices), whichare connected to the Data Highway Plus Bridge Module (DH485, DH, or DF1).The DAServer does not require the Rockwell Software RSLinx OEMpackage.While the DAServer is primarily intended for use with Wonderware InTouch ®(version 7.11 Patch 02 and later), it may be used by any Microsoft Windowsprogram capable of acting as a DDE, FastDDE, SuiteLink , or OPC client.ABDHPLUS DAServer User’s Guide

Introduction 11DDE is a communications protocol developed by Microsoft to allowapplications in the Windows environment to send/receive data and instructionsto/from each other. It implements a Client/Server relationship between twoconcurrently running applications. The server application provides the data andaccepts requests from any other application interested in its data. Requestingapplications are called clients. Some applications such as InTouch andMicrosoft Excel can simultaneously be both a client and a server.NetDDE is a communications protocol that extends the standard DDEfunctionality to include communications over local area networks and throughserial ports. Network extensions are available to allow DDE links betweenapplications running on different computers connected via networks ormodems. For example, NetDDE supports DDE between applications runningon IBM-compatible computers connected via LAN or modem, and DDE-awareapplications running on non-IBM-compatible computers under operatingenvironments such as VMS and UNIX.Bus Communications ProtocolsSeveral types of bus communications protocols are utilized by theABDHPLUS DAServer to communicate with the controllers.• Data Highway Plus• Bridge Module• DH-485• DH• DF1Note DH485, DH, and DF1 are only supported in the bridge modules.The Data Highway Plus is a Local Area Network (LAN) that allows peer-topeercommunications among a maximum of 64 nodes. It is used when aconnection of a small number of nodes on a common link or one network isneeded. The Data Highway Plus is used by both the PLC-5 and SLC 500families of controllers for a connection to the adapter card.The other type of module the controllers are connected to is the BridgeModule. The bridge module provides communications to the Allen-BradleyPLC-5 or SLC 500 families of controllers that are located in two differentnetworks, connected to one or another to the PCI adapters (1784-PKTx or1784-PKTxD or SST 5136-SD), through various Data Highway Plus, DH485,DH, RS-232 asynchronous link, using Allen-Bradley bridge modules (1785-KA5, 1785-KA, or 1785-KE).Important! The DAServer will support PCI adapters in any particularsystem. The DAServer will not support a mixture of cards, from differentvendors, in the same computer.ABDHPLUS DAServer User’s Guide

12 Chapter 1Accessing Items via the DAServerThe method for accessing items through the DAServer depends on thecommunications protocol being used.In the case of OPC communications, the protocol addresses an element of datain a conversation with six characteristics: node name, program name, groupname, device group, link name, and item name.• The node name (required for remote access) and device group areoptional.• A fully qualified OPC Item name (ItemID) is composed of the link nameand item name.• All other characteristics are specified through separate DAServer means.To access an OPC item, the OPC client needs to connect to the DAServer(either in-process or out-of-process) and create an OPC group defining thedata-acquisition properties for the collection of items to be added. OPC groupscan be either public or private. Public OPC groups are shared across multipleclients, whereas private OPC groups are local to a single client. Optionally adevice group, which indicates the access path to the items for read/write, canbe specified from the DAServer.The following briefly describes each characteristic of the OPC protocol:• node name: Computer (host) name identifying a specific node on thenetwork (for Remote Access ONLY).• program name: The registered OPC server name uniquely identifying aspecific server (ProgID). For this DAServer, the program name isArchestrA.DASABDHPLUS.1.• group name: The OPC group created from the client for organizing acollection of items logically with the same data-acquisition propertiesbetween the client and the server, such as update rate.• device group: Meaningful names configured in the DAServer under aspecific controller for the common custom attributes between theDAServer and the device, such as update interval. If not specified from theclient, the default device group using the global-configuration attributevalues from the DAServer is assumed. Functionally, a device group isequivalent to an access path (optional).• link name: The set of hierarchy node names, representing the specificdevices on a communications path link from the hierarchy root to aspecific controller as configured for this DAServer under the DAServerManager, separated by delimiters.• item name: A specific data element, the leaf of the hierarchy tree of thisDAServer, within the specified group. For example, when using thisDAServer, an item can be a relay, timer, counter, register, and so on., in thecontroller.In the case of DDE/SuiteLink communications, the protocol addresses anelement of data in a conversation that uses a four-part naming convention thatincludes the node name, application name, topic name, and item name. Thefully qualified DDE/SuiteLink naming convention includes all four parts,although the node-name part (required for remote access only) is optional.ABDHPLUS DAServer User’s Guide

Introduction 13The following briefly describes each portion of this naming convention:• node name: Computer (host) name identifying a specific node on thenetwork (for Remote Access ONLY).• application name: The name of the Windows program (this DAServer)that will be accessing the data element. In the case of data coming from orgoing to Allen-Bradley devices via the DDE/SuiteLink PlugIn of thisDAServer, the application name portion of the address isDASABDHPLUS.• topic name: Meaningful names are configured in the DAServer to identifyspecific devices. These names are then used as the topic names in allconversations with that device. For example, ABPLC. Topic name mapsto a device group defined in the DAServer.Note You can define multiple device group (topic) names for the samedevice (PLC) to poll different points at different rates.• item name: A specific data element within the specified topic. Forexample, when using this DAServer, an item can be a relay, timer, counter,register, and so on, in the PLC.Note The term "point" is used interchangeably with the term "item" inthis user's guide.For more information on item/point names, see the "Item Names" sectionof this user's guide.FeaturesDemo ModeThe Wonderware ABDHPLUS DAServer provides the following features:• The ability to communicate over multiple application-level protocols atthe same time.• The ability to add new application-level protocols on the fly.• The ability to be configured remotely.• New, robust diagnostic abilities.For more in-depth information on the DAServer architecture, see theReference section.You can install a fully functioning version of this DAServer for demonstrationpurposes without a license. Demo mode allows you to test the functionality ofthe DAServer for 120 minutes. After that time, you must install a license tocontinue using the DAServer.ABDHPLUS DAServer User’s Guide

14 Chapter 1When you first start this DAServer, it checks for a license. If the DAServercannot find a valid license installed on the local computer, it logs a warningmessage indicating a valid license cannot be retrieved, and enters Demo mode.Thereafter, the DAServer repeats its request for the license every 30 seconds. Ifno license is found, the DAServer again logs a warning message on the issue.This process is repeated for 120 minutes, after which the DAServer stopsupdating Read/write on all device items (read from cache is allowed, but allnon-system data would receive Bad quality status). The DAServer continues torequest for a license. Clients continue to function normally (for instance, youcan still add or remove an item, but its quality is set to Bad until a license isobtained).Note Use the $SYS$Licensed system item, a read-only Boolean item, tocheck the status of your license: True for Licensed and False for Not Licensed.If you subsequently add a license to the License Manager, the DAServer logs amessage acknowledging the license, switches out of Demo mode, and runsnormally.Note Once a DAServer obtains a valid license, it no longer checks for alicense. Thus, if your license expires, your DAServer would cease to functionbut this condition would not be logged until the next restart of the DAServer.ABDHPLUS DAServer User’s Guide

Configuration 15CHAPTER 2ConfigurationAfter the adapter-card installation, the driver for the card needs to be installed.In this section, a step-by-step procedure for this card-driver installation isincluded.Once the Wonderware ABDHPLUS DAServer has been installed, a smallamount of configuration is required. This configuration is performed using theDAServer Manager hosted in the System Management Console after it isstarted through the Programs menu of the Windows Start button.Before the DAServer is cativated, the device hierarchy, simulating the physicalhardware layout, must first be built to establish communications to each of thecontrollers. Once the ABDHPLUS hierarchy has been built, the respectivedevices for communications can be configured. Finally, the desired DeviceGroups for each controller may be created.Contents• Installing the Card Driver• Getting Started Quickly with the DAServer• Configuring the DAServer• ABDHPLUS Hierarchy in the DAServer Manager• Configuring Device Group Definitions• Archiving Configuration Sets• Hot ConfigurationInstalling the Card DriverAfter the adapter card (either PKTX/PKTXD card or SSTPCI card) has beeninstalled, the computer will ask for its driver to be installed. The installation ofthe card driver is performed with the help of the Found New Hardware Wizard.To install the card driver1. From the Wizard’s Welcome to the Found New Hardware Wizard page,click on the option button, Install from a list or specific location(Advanced).ABDHPLUS DAServer User’s Guide

16 Chapter 22. Click the Next button.• The Wizard will ask you to choose your search and installationoptions.3. Enter the path where the driver file is located.• The following driver files are provided for you.• The ab1784kt.inf file for the PKT card.ABDHPLUS DAServer User’s Guide

Configuration 17• The ss5136sd.inf for the SSTPCI card.• These two files are located in the same directory as the DAServerSetup.exe file.4. After the respective driver-file path has been entered, click the Nextbutton.• The Wizard will let you know that the driver for the card has beeninstalled.When the card-driver installation is completed, you can start the preparationsof the DAServer for use.Getting Started Quickly with the DAServerThis section briefly describes the procedures required to prepare theABDHPLUS DAServer for use. Detailed descriptions of each step can befound in the following sections of this documentation. This section is intendedfor people who are familiar with DAServers.Note If you are not familiar with the DAServer functionality, please proceedto the more-detailed procedures following this section.To prepare the ABDHPLUS DAServer1. Install the Wonderware ABDHPLUS DAServer on Windows by runningthe Setup.exe program.Note In addition to the DAServer, the drivers of the respective cards are alsoautomatically installed.ABDHPLUS DAServer User’s Guide

18 Chapter 2Note The DAServer installation instructions are included in a separate Helpfile (.chm extension).• Accept all the default settings during installation.Note Since there are no default values for security settings, you must takenote of the User Name and password selected during the install.2. Start the ABDHPLUS DAServer by selecting the Programs menu fromthe Start button on the taskbar.3. Navigate to the Wonderware folder that contains the SystemManagement Console, then click System Management Console.4. From the System Management Console, find the ABDHPLUS DAServerin the DAServer Manager tree, the location in which it is installed.• Under the Local Node, the DAServer name isArchestrA.DASABDHPlus.1.• See the DAServer Manager Online Help for general informationabout working in this snap-in environment.5. The new ABDHPLUS DAServer must now be configured.• Before proceeding, determine the hierarchical structure of thenetwork/PLC environment to which you plan to connect.6. Right-click the Configuration branch of the hierarchy, and select one ofthe two CARD Objects (representing the adapter cards for the AllenBradley or SST processor types):PKT_CARD objectSSTPCI_CARD objectNote Multiple PKT_CARD or SSTPCI_CARD objects can be created for theDAServer by right-clicking the Configuration object and selecting AddPKT_CARD Object or Add SSTPCI_CARD Object from the shortcutmenu.In this step, in addition to Step 7, the hierarchy entry is added in "editmode," providing a convenient place for you to appropriately describecomponents of your specific hardware environment.• If the object is not renamed at this time, a numeric sequencing systemis applied.• Any hierarchy entry can be renamed at a later time.Important! The DAServer will support PCI adapters in any particularsystem. The DAServer will not support a mixture of cards, from differentvendors, in the same computer.7. Right-click on the selected CARD object, and select the appropriate itemfrom five selections, each of which represents the PLC or bridge moduleused to connect to the adapter card:ABDHPLUS DAServer User’s Guide

Configuration 19PLC5_DHP objectSLC500_DHP objectM1785KEBR objectM1785KA objectM1785KA5 objectNote Multiple PLC5_DHP, SLC500_DHP, M1785KEBR, M1785KA, andM1785KA5 objects can be created for each CARD object by right-clicking onthe selected New__CARD_000 object in the higher tree branch, andselecting Add Object from the shortcut menu, respectively.• Up to 63 of objects, under the adapter card, can be added to thehierarchy.• PLC-5 and SLC 500 objects represent the logical end points for thehierarchy being configured; they have no configurable child objects.Note The Data Highway Plus allows peer-to-peer communications among amaximum of 64 nodes, including the adapter card and bridge module.8. Configure the respective device objects created in the preceding steps withthe appropriate parameter values, if applicable.9. Optionally, create the desired device groups in the Device Groups dialogbox of each logical end-point object.Note When any configuration view is in an open state and you open the sameserver the second time, the DAServer locks the second instance of this sameserveraccess for any update or configuration activities. Access to this secondopening instance will resume after the first one has been closed.The DAServer is now ready for use. In order to use the DAServer, you mustactivate it.• If you are using an OPC Client, the DAServer will auto-start.• If you are using DDE/SuiteLink, you must start the DAServer eitheras a manual or automatic service.• To activate the DAServer, right-click onArchestrA.DASABDHPlus.1 and select Activate Server from theshortcut menu.Note To run the ABDHPLUS DAServer as a service, use the shortcut menuon the DAServer name and select Configure As Service. You can configure itas an auto service or manual service. For more information about configuringthe DAServer as a service, see the Activation/Deactivation/Service Componentof the DAServer Manager documentation.ABDHPLUS DAServer User’s Guide

20 Chapter 2Configuring the DAServerNote This DAServer is hosted by the DAServer Manager, a MicrosoftManagement Console (MMC) snap-in, which is part of the ArchestrA SystemManagement Console (SMC) suite of utilities. Many high-level functions anduser-interface elements of the DAServer Manager are universal to allDAServers, and only the documentation for the DAServer Manager containsdescriptions of those universal functions/UI elements. Therefore, reading thedocumentation for both the MMC and the DAServer Manager is critical tounderstanding this user’s guide. To read the documentation about the MMCand DAServer Manager, right-click on the DAServer Manager icon and selectthe Help menu. Both the MMC and DAServer Manager Help is displayed.Select the appropriate Help topics. An Adobe Acrobat version of the DAServerManager documentation (DAServerManager.pdf) is also provided.Note The shortcut menu items described in this document typically representonly a subset of any actual shortcut menu. Most items in each shortcut menuare standard Windows commands. For more information about thosecommands, please see Help by right-clicking the System ManagementConsole icon.Before it can be configured, the Wonderware ABDHPLUS DAServer has to beinstalled on Windows.To prepare the ABDHPLUS DAServer1. Install the Wonderware ABDHPLUS DAServer on Windows by runningthe Setup.exe program.Note In addition to the DAServer, the drivers of the respective cards are alsoautomatically installed.Note The DAServer installation instructions are included in a separate Helpfile (.chm extension).2. Accept all the default settings during installation.Note Since there are no default values for security settings, you must takenote of the User Name and password selected during the install.3. After it has been installed, start the System Manager Console by clickingthe Start button on the Windows taskbar, and pointing to Programs.4. Point to the Wonderware folder that contains the System ManagementConsole, then click System Management Console.5. From the System Management Console tree, click on DAServerManager.6. Click on Local Domain, then Local Node.• Under the Local Node, the DAServer name isArchestrA.DASABDHPlus.1.ABDHPLUS DAServer User’s Guide

Configuration 21• See the DAServer Manager documentation for general informationabout working in this snap-in environment.7. Before the DAServer is started, the device hierarchy must be built toestablish communications to each of the controllers.Note For step-by-step procedures on building the device hierarchy, please seethe section, "ABDHPLUS Hierarchy in the DAServer Manager."Note Selecting the Configuration object of the hierarchy tree displays theglobal parameters interface for this DAServer. The default Poke Mode settingsfor the DAServer is Transition mode. Configure all other global parameters asrequired for this DAServer. For more information about the Global Parametersdialog box, including descriptions of the different Poke Modes, see theDAServer Manager documentation. You can access that documentation byright-clicking on the DAServer Manager icon, clicking the Help topics on theHelp menu, and then navigating through the DAServer Manager book.Important! Any Global Parameters that appear dimmed are not supported.8. When the ABDHPLUS hierarchy build has been completed, you can startconfiguring the respective devices for communications.9. Finally, you may create the desired Device Groups for each controller by:• Navigating to the object of interest in the DAServer Manager treeview.• Clicking on the Device Groups tab.Note For step-by-step procedures on configuring Device Groups, please seethe section, "Configuring Device Group Definitions."ABDHPLUS DAServer User’s Guide

22 Chapter 2Note When any configuration view is in an open state and you open the sameserver the second time, the DAServer locks the second instance of this sameserveraccess for any update or configuration activities. Access to this secondopening instance will resume after the first one has been closed.The DAServer will be ready to use after it is activated.• If you are using an OPC Client, the DAServer will auto-start.• If you are using DDE/SuiteLink, you must start the DAServer either as amanual or automatic service.• The DAServer can be activated by right-clicking onArchestrA.DASABDHPlus.1 and selecting Activate Server from theshortcut menu.Note To run the ABDHPLUS DAServer as a service, right-click on theDAServer name and select Configure As Service from the shortcut menu.You can configure it as an auto service or manual service. For moreinformation about configuring the DAServer as a service, see theActivation/Deactivation/Service Component of the DAServer Managerdocumentation.ABDHPLUS Hierarchy in the DAServer ManagerNote Before attempting to configure your DAServer, you should determinethe hierarchical structure of your network/PLC environment.The server-specific configuration portion of the ABDHPLUS DAServerhierarchy tree under the DAServer Manager starts at the CARD object.• This is the place in the DAServer hierarchy for configuring the adaptercards for the Allen Bradley or SST processor types.• Rename this object as appropriate.Important! The DAServer will support PCI adapters in any particularsystem. The DAServer will not support a mixture of cards, from differentvendors, in the same computer.Important! If you subsequently clear your configuration hierarchy, you mustcreate each of these CARD objects by right-clicking on the Configurationobject and selecting the Add _CARD Object in the shortcut menu,respectively. A New__CARD_000 object is created. Rename asappropriate. From this point, all of the following instructions apply.CARD ObjectsTwo CARD objects can be created in the initial level of the ABDHPLUSDAServer hierarchy in the DAServer Manager. Each CARD objectconfiguration view is the place in the hierarchy to configure the differentadapter cards for the Allen Bradley or SST processor types.ABDHPLUS DAServer User’s Guide

Configuration 23The two CARD objects supported by the DAServer are as follows:• PKT_CARD object – More than one PKT_CARD object can be created,and each one of them represents either the 1784-PKTx or 1784-PKTxDadapter card.• SSTPCI_CARD object – Multiple SSTPCI_CARD objects can becreated for the DAServer, with each one of them representing the SST5136-SD-PCI adapter card.To create a CARD object from the Configuration branch1. Right-click on Configuration.2. Select the appropriate Add _CARD Object from the shortcutmenu.• Each object can be renamed when it is created in the hierarchy, or at alater time.3. Rename each of the newly created object as appropriate.The following figure shows the CARD objects in the Configuration branch ofthe hierarchy.PKT_CARD ObjectThe New_PKT_CARD_000 Parameters configuration view is used toconfigure the Allen Bradley 1784-PKTx or 1784-PKTxD PCI-type adapters. Amaximum of 4 (four) PKT_CARD objects can be configured.ABDHPLUS DAServer User’s Guide

24 Chapter 2The New_PKT_CARD_000 Parameters configuration view has eightelements, seven of which are configurable.• Processor Type: The information is provided automatically by theDAServer Manager.• In this case, the processor type is AB 1784-PKTx (PCI).• DH Plus Node Address: Select the unique Node Address on the DataHighway Plus network.• The maximum octal number allowed for this address is 77.• The minimum value is 0 (zero).• The default value is 1 (one).• Firmware Path: Enter the path of the file containing the firmware.• The maximum number of characters that can be used is 255.• The default path of the file is: C:\Program Files\Wonderware\DAServer\DASABDHPLUS\Bin\Firmware.• PCI Card: Select the adapter card from the list.• Maximum Queued Messages: Set the maximum number of messages tobe queued.• Valid range should be 1 (one) to 4 (four).• The default number is 4 (four).• Connection Timeout: Determine the time allowed to establish aconnection to a device.• The default value is 15 seconds.ABDHPLUS DAServer User’s Guide

Configuration 25• Valid range is 1 (one) to 300 seconds.• Baud Rate: Set the Baud rate either to 57.6 K Baud or 230.4 K Baud.• The standard or default rate is 57.6 K Baud.• Terminating Resistor Enabled: Enable the terminating resistor when theadapter is the first or the last physical station on the Data Highway Plus.SSTPCI_CARD ObjectThe configuration of the SST 5136-SD-PCI-type cards takes place in theNew_SSTPCI_CARD_000 Parameters configuration view. A maximum offour (4) cards can be added to the configuration.There are six elements in this New_SSTPCI_CARD_000 Parametersconfiguration view that are configurable.• Processor Type: The DAServer Manager automatically provides theinformation.• In this case, the processor type is SST 5136-SD (PCI).• DH Plus Node Address: Select the unique Node Address on the DataHighway Plus network.• The maximum octal number allowed for this address is 77.• The minimum value is 0 (zero).• The default value is 1 (one).• Firmware Path: Provide the path of the file containing the firmware.ABDHPLUS DAServer User’s Guide

26 Chapter 2• The default file location is C:\Program Files\Wonderware\DAServer\DASABDHPLUS\Bin\Firmware.• The maximum number of characters allowed is 255.• PCI Card: Select the adapter card from the list.• Maximum Queued Messages: Set the maximum number of messages tobe queued.• The valid range should be 1 (one) to 4 (four).• The default number is 4 (four).• Connection Timeout: Determine the time allowed to establish aconnection to a device.• Valid range is 1 (one) to 300 seconds.• The default value is 15 seconds.• Baud Rate: Set the Baud rate to either 57.6 K Baud, or 115.2 K Baud, or230.4 K Baud..• The default rate is 57.6 K Baud.PLC and Bridge-Module ObjectsThe following five PLC and Bridge-Module objects can be created from theNew PKT_CARD_000 and SSTPCI_CARD_000 branches of the DAServerhierarchy:• PLC5_DHP Object – Multiple PLC5_DHP objects can be created foreach _CARD object. The DHP object represents the DataHighway Plus used for connecting the PLC-5-family controllers to theadapter card.• SLC500_DHP Object – Multiple SLC500_DHP objects can be createdfor each _CARD Object. The DHP object represents the DataHighway Plus used for connecting the SLC500-family controllers to theadapter card.• M1785KEBR Object – Multiple M1785KEBR objects can be created foreach _CARD object. Each represents the Allen-Bradley Data-Highway-Plus-to-RS-232-to-Data-Highway-Plus bridge module, 1785-KEBR, which is used for the PLC-5 families of controllers to connect tothe adapter card.• M1785KA Object – Multiple M1785KA objects can be created for each_CARD object. Each object represents the bridge module 1785-KA, which is connecting the PLC-5 families of controllers to the DataHighway Plus to the Data Highway and to another Data Highway Plushaving the connection to the adapter card.• .M1785KA5 Object – Multiple M1785KA5 objects can be created foreach _CARD object. Each represents the Allen-Bradley bridgemodule 1785-KA5 that is utilized for the SLC 500 controllers to connectto the adapter card through DH485 and Data Highway Plus.ABDHPLUS DAServer User’s Guide

Configuration 27To add PLC and Bridge-Module objects to the hierarchy1. Right-click on your New__CARD_000 branch.2. Select Add Object.3. Rename as appropriate.PLC5_DHP ObjectThe newly created PLC5_DHP_000 Parameters configuration view is theplace in the DAServer hierarchy where the Data Highway Plus, used forconnecting the PLC-5-family controllers to the adapter card, is configured.ABDHPLUS DAServer User’s Guide

28 Chapter 2The configuration view contains three configurable parameters:• DH Plus Node Number: Select the Data Highway Plus node number.• The maximum octal number allowed for this address is 77.• The default value is 1 (one) octal.• Message Packet Size: Determine the message packet size for the PLC-5controller on the Data Highway Plus.• The valid range is 2 (two) to 240 bytes.• The default value is 216 bytes.• Reply Timeout: Enter the maximum amount of time that the DAServerwill wait for a response from the PLC.• The default value is 15 seconds.• Valid range is 1 (one) to 300 seconds.SLC500_DHP ObjectThe newly created SLC500_DHP_000 Parameters configuration view is usedto configure the Data Highway Plus used for connecting the SLC500-familycontrollers to the adapter card.Three configurable elements can be found in the configuration view:• DH Plus Node Number: Select the Data Highway Plus node number.• The maximum octal number allowed for this address is 77.• The default value is 1 (one) octal.ABDHPLUS DAServer User’s Guide

Configuration 29• Message Packet Size: Set the size of the message packet for the SLC 500controller on the Data Highway Plus.• The default value is 216 bytes.• Valid range is 2 (two) to 240 bytes.• Reply Timeout: Enter the maximum amount of time that the DAServerwill wait for a response from the PLC.• The default value is 15 seconds.• Valid range is 1 (one) to 300 seconds.M1785KEBR ObjectThe New_M1785KEBR_000 Parameters configuration view is used toconfigure the Allen-Bradley 1785-KEBR, a Data-Highway-Plus-to-RS-232-to-Data-Highway-Plus bridge module, which is utilized for the PLC-5 families ofcontrollers to connect to the adapter card.The configuration view contains one configurable element, as follows:• DH Plus Node Number: Select the Data Highway Plus node number.• The maximum octal number allowed for this address is 77.• The default value is 1 (one) octal.M1785KA ObjectThe New_M1785KA_000 Parameters configuration view is used toconfigure the 1785-KA bridge module, which is connecting the PLC-5 familiesof controllers from the Data Highway Plus to the Data Highway, throughM1785-KABR module, and to another Data Highway Plus that has theconnection to the adapter card.ABDHPLUS DAServer User’s Guide

30 Chapter 2The configuration view contains the following configurable element:• DH Plus Node Number: Select the Data Highway Plus node number.• The maximum octal number allowed for this address is 77.• The default value is 1 (one) octal.M1785KABR ObjectThe New_M1785KABR_000 Parameters configuration view is used toconfigure the 1785-KABR bridge module, which is connecting the PLC-5families of controllers from the Data Highway Plus to the Data Highway.ABDHPLUS DAServer User’s Guide

Configuration 31This configuration view contains the following configurable element:• DH Node Number: Select the Data Highway node number.• The maximum octal number allowed for this address is 77.• The default value is 1 (one) octal.M1785KA5 ObjectThe New_M1785KA5_000 Parameters configuration view is the place in theDAServer hierarchy to configure the Allen-Bradley bridge module 1785-KA5,which is utilized for the SLC 500 controllers to connect to the adapter cardthrough DH485 and Data Highway Plus.One element in this configuration view needs to be configured:• DH Plus Node Number: Select the Data Highway Plus node number.• The maximum octal number allowed for this address is 77.• The default value is 1 (one) octal.Note The default name created from adding a hierarchy object is in the formatof New_ObjectName_###, where ObjectName is the name of the object typeand ### is a numeric value starting from "000" enumerated sequentially perhierarchy object. The link name for the OPC items is constructed byassembling the respective object names of the nodes along the hierarchy tree inthe logical order, starting from this DAServer’s CARD Object root down to theleaf. Therefore, the link name is always unique for the DAServer.Note In order to use the DAServer, you must activate it. See the DAServerManager documentation for information about how to activate and deactivatethe DAServer.ABDHPLUS DAServer User’s Guide

32 Chapter 2Configuring Device Group DefinitionsThe Device Groups tab in the DAServer Manager user interface is used tocreate new, modify, or delete device group definitions for an object. ForDDE/SuiteLink communications, one or more device group definitions mustexist for each PLC that the DAServer will communicate with.Important! For DDE/SuiteLink, it is strongly recommended that each devicegroup (topic) definition contain a unique name. The OPC, however, has theflexibility to use any names, including duplicate names, for the device groupdefinitions.Device Group DefinitionsThe Device Groups dialog box, which is displayed by clicking the DeviceGroups tab in the PLC5_DHP Object and SLC_500_DHP Objectconfiguration views, is the place to add device groups, delete and define devicegroups, configure default update intervals for the objects, and also edit updateintervals.Note When you add a new device group, enter a unique name (up to 32characters long). When you select another part of the DAServer tree hierarchy,you are prompted to save the modifications to the configuration set.To create or add device groups1. To create or add device groups, right-click in the Device Groups box.2. Select the Add command from the shortcut menu.• When you add a new device group, enter a unique name (up to 32characters long).ABDHPLUS DAServer User’s Guide

Configuration 33To make edits on device groupsThe device group’s name or update interval for an object can be edited asfollows:• In the Name column, double-click on the device group’s name to be editedand make the edit.• Double-click on the device group’s value to be edited in the UpdateInterval column, and make the edit.To delete device groups• Deleting a device group from the list can be performed by right-clickingon the device group to be deleted, and then selecting the Delete commandfrom the shortcut menu.Note When you select another part of the ABDHPLUS DAServer treehierarchy, you are prompted to save the modifications to the configuration set.To configure default update intervals1. To configure a default update interval for the object, right-click in theDevice Groups box.2. Select Config Default Update Interval from the shortcut menu.To edit update intervals• To edit the update interval for an object, double-click its value in theUpdate Interval column and make the edit.• Update Interval is the frequency (in milliseconds) that the DAServeracquires data from the topics associated with that device group.• Different topics can be polled at different rates in a PLC by definingmultiple device-group names for the same PLC and setting a differentUpdate Interval for each device group.Note When you select another part of the ABDHPLUS DAServer treehierarchy, you are prompted to save the modifications to the configuration set.Each configuration view associated with objects in the DAServer hierarchytree has a common feature, the Apply button.1. When you modify any Parameters or Device Groups dialog box, clickApply to implement the new modifications.• If you do not click Apply, the configuration is reset to its originalcondition (since the last save).2. After all modifications, you must save when prompted for the new data tobe saved to the configuration set.Scan-Based Message HandlingWonderware's DAServers are based on the concept of polling a hardwaredevice for information. This polling is driven by a need which is expressed inthe form of requests from one or more clients.ABDHPLUS DAServer User’s Guide

34 Chapter 2For DDE/SuiteLink, once a particular piece of information has been requestedby a client, the DAServer formulates its own request and sends that request tothe hardware device. The DAServer then waits for a response to its request.Once the information has been received, the DAServer passes that informationback to the client, and repeats the process until all clients have ceasedrequesting information. The rate at which the DAServer will poll a particulardevice for a specific piece of information is defined in the device group (topicdefinition) inside the DAServer, using a parameter called the Update Interval.When setting this parameter, there is always a trade-off between the updatespeed of the device group and the resulting decrease in system responsiveness.If you use OPC interface, in addition to the capabilities described in thepreceding paragraph, the OPC Client also has additional capabilities on UpdateInterval control.Since you more than likely want very fast response, the temptation is to set theUpdate Interval to a value close to 0 (zero) seconds. However, if every point ispolled at this rate, the entire system will suffer due to slow response time.Therefore, you should compromise, and set the Update Interval to a morereasonable value. You could also create multiple device groups for eachdevice, setting the Update Interval to different values, then assigning differentitems to different device groups depending on how quickly the values changeand how quickly you want to see an update of those changes.Some items, like alarms, change very infrequently, but because of theirimportance require very fast updates. For those kinds of items, you should setthe Update Interval at a very small value. If you desire an immediate response,set the Update Interval at 1 (one).Unsolicited Message HandlingIn the world of PLCs and DAServers it is obvious, to even the most casualuser, that a PLC will know when a critical event has occurred before theDAServer will have a chance to poll for that data. Therefore, it would seemnatural that if a critical event occurs, the PLC should have the capability toinform the DAServer immediately, without having to wait for the DAServer topoll it.This is the role of an unsolicited message. Once a PLC has determined that acritical condition exists, it can generate a "reply" message to a poll which neveroccurred. In other words, it can answer the DAServer's question before theDAServer has a chance to ask it.The ABDHPLUS DAServer supports the following unsolicited messages:• Peer-to-Peer: This method involves DHP-address-to-DHP-addresscommunications.• Configure which computer (by its DHP address) receives unsolicitedmessages in your client application.• Two instances of peer-to-peer unsolicited messages are generated bythe DAServer:• If the value of "Update Interval" for a topic is 0 (zero), the serverwill poll this topic only once at the start. After that, only anunsolicited message will update the data.ABDHPLUS DAServer User’s Guide

Configuration 35• If the value of "Update Interval" for a topic is >0 (zero), theserver will update the data for a particular item immediately uponreceiving an unsolicited message for the item. The DAServer willalso update the data at every Update Interval.Note For a more specific Allen Bradley definition of peer-to-peer unsolicitedmessaging, please refer to the Allen-Bradley PLC-5 Family documentation.To receive unsolicited messages• Set a device group’s "Update Interval" to 0 (zero).To access the settings for device groups1. Click on the PLC’s name in the Configuration hierarchy of yourDAServer.2. Select the Device Groups tab of the configuration view pane at right.3. Double-click the number in the Update Interval column of the desireddevice group and type the number 0 (zero).• You are prompted to save the configuration change when you accessanother part of the DAServer hierarchy tree.Archiving Configuration SetsAfter you have configured your DAServer, you can archive that specificconfiguration. You can archive more than one configuration set, andsubsequently choose different configurations for different purposes.To archive configuration sets1. In the DAServer Manager, right-click on the Configuration node in thehierarchy below your DAServer.2. Select Archive Configuration Set from the shortcut menu.3. In the Archive Configuration Set configuration view, provide aConfiguration Set Name and click Archive.• All current configuration values are saved to the archived set.Once you have archived at least one configuration set, you can select it for use.To use different configuration sets from the current one1. In the DAServer Manager, right-click the Configuration node in thehierarchy below your DAServer.2. Select Use Another Configuration Set from the shortcut menu and clickon a configuration set in the sub-menu.• All parameters in the DAServer configuration hierarchy change to thechosen configuration set.ABDHPLUS DAServer User’s Guide

36 Chapter 2Hot ConfigurationThe ABDHPLUS DAServer is hot-configurable. Incorporated in the DAServerare the following hot-configuration functionalities:• Modifying Global Configuration parameters.• Adding, deleting, or modifying device nodes (without affecting any otherdevice nodes, excluding the children of the modified device nodes).• Adding, deleting, or modifying device groups.Limited support is provided for the hot configuration for the server-specificconfiguration parameters in this release. You can modify server-specificparameters while the server is active. However, to have those changes takeeffect, you have to restart the DAServer.Note If changes are made to server-specific parameters while the server isactive, the DAServer will issue a warning message to the logger.ABDHPLUS DAServer User’s Guide

Item Names 37CHAPTER 3Item NamesThe Wonderware ABDHPLUS DAServer currently supports item names thatfollow the conventions described for PLC-5-series and SLC 500-seriescontrollers. This chapter describes the item naming conventions for thesedevices.Contents• PLC-5 Item Naming• SLC 500 Item Naming• DAServer Standard System Items• Generic OPC SyntaxPLC-5 Item NamingThe general format of item names for data from PLC-5 controllers matches thenaming convention used by the programming software. In the followingformat, the parts of the name shown in square brackets ([]) are optional.[$] X [file] : element [.field] [/bit]$ – Purely optional.X – Identifies the file type.file # – File number (0 - 999 decimal).File 0 must be Output.File 1 must be Input.File 2 must be Status.element – Element number within the file.For Input and Output files it must be 0 - 777 octal.For all other file types, it must be 0 - 999 decimal..field – Valid only for Counter, Timer, ASCII String, PID, SFC Status, BlockTransfer, and Control files. Refer to the preceding table./bit – Valid for all file types except ASCII String and Floating Point.For Input and Output files it must be 0 - 17 octal.For all other file types it must be 0 - 15 decimal.ABDHPLUS DAServer User’s Guide

38 Chapter 3The following table summarizes the valid file types, the default file number foreach type, and the fields allowed (if any):X File TypeDefaultFile #.fieldsO Output 0 N/AI Input 1 N/AS Status 2 N/AB Binary 3 N/AT Timer 4 .PRE .ACC .EN .TT .DNC Counter 5 .PRE .ACC .CU .CD .DN .OV .UNR Control 6 .LEN .POS .EN .EU .DN .EM .ER.UL .IN .FDN Integer 7 N/AF Floating Point 8 N/AA ASCII None N/AD BCD None N/AST ASCII String* None .LENPD PID* None .ADRF .ADRE .BIAS .CA .CL .CT.DB .DO .DVDB .DVN .DVNA.DVP .DVPA .EN .ERR .EWD .INI.KD .KI .KP .MAXI .MAXO .MAXS.MINI .MINO .MINS .MO .OLH.OLL .OUT .PE .PV .PVDB .PVH.PVHA .PVL .PVLA .PVT .SO .SP.SPOR .SWM .TIE .UPDSC SFC Status* None .DN .ER .FS .LS .OV .PRE .SA .TIMBT Block Transfer*(Read Only)None .EN .ST .DN .ER .CO .EW .NR .RW.TO .RLEN .DLEN .FILE .ELEM* Available only on certain PLC-5 models. Check the Processor Manual for the model being used.Output File ItemsO[n]:rg[/b]n represents the file number, which is optional. Ifspecified, it must be 0 (zero).r indicates the rack number (0 - 27 octal).g indicates the I/O group (0 - 7 octal).b specifies the bit (0 - 17 octal). /b may be omitted ifnecessary to treat the I/O group as a numeric value.Examples:O0:00/0ABDHPLUS DAServer User’s Guide

Item Names 39Input File Items$O:177/17O:3 4BCD (for 16-bit 7-segment display)I[n]:rg[/b]n represents the file number and is optional. Ifspecified, it must be 1.r indicates the rack number (0 - 27 octal).g indicates the I/O group (0 - 7 octal).b specifies the bit (0 - 17 octal). /b may be omitted, ifnecessary, to treat the I/O group as a numeric value.Examples:I1:0/0I:177/17I:3 4BCD (for 16-bit thumbwheel input)Status File ItemsS[n]:e[/b]n represents the file number and is optional. Ifspecified, it must be 2.e indicates the element number in the file.b is optional. If specified, it indicates the bit (0 - 15decimal).Note Refer to the 1785 PLC-5 Family Processor Manual (Allen-BradleyPublication 1785-6.8.2) for a complete description of the status fileinformation.Examples:$S:18 (year)$S2:18 (year)S2:19 (month)S2:10/0 (battery low status bit)ABDHPLUS DAServer User’s Guide

40 Chapter 3Binary File ItemsB[n]:e[/b] orB[n]/mExamples:B:33B:6/4B:3/15999n represents the file number and is optional. If notspecified, it is assumed to be 3. If specified, the filenumber must be 3 - 999 decimal.e specifies the element (word) number within the Binaryfile. It must be 0 - 999 decimal.b specifies the bit number within the word and isoptional. In the first form (where :e is present), the bitnumber must be 0 - 15 decimal.m specifies the bit number within the file. However, inthe second form, no word numbers are specified and thebit number may be 0 - 15999.(same bit as B/100)(same bit as B:999/15)Timer File ItemsT[n]:e[.f][/b]n represents the file number and is optional. If notspecified, it is assumed to be 4. If specified, the filenumber must be 3 - 999 decimal.e specifies the element number (three words per element)within the Timer file. It must be 0 - 999 decimal..f identifies one of the valid Timer fields. The validfields for Timer Files are listed in the table. If .f isomitted, it is assumed to be the word containing thestatus bits.b is optional and is normally not used. All of the fields ofa timer can be accessed by specifying the .f fields.However, it is possible to use /b to single out a bit in the.PRE or .ACC fields (which are words). For Timer files,the bit number must be 0 - 15 decimal.Examples:T4:0.ACCT4:0.DNT4:1.PREABDHPLUS DAServer User’s Guide

Item Names 41Counter File ItemsC[n]:e[.f][/b]n represents the file number and is optional. If notspecified, it is assumed to be 5. If specified, the filenumber must be 3 - 999 decimal.e specifies the element number (three words perelement) within the Counter file. It must be 0 - 999decimal..f identifies one of the valid Counter fields. The validfields for the Counter files are listed in the table. If .f isomitted, it is assumed to be the word containing thestatus bits.b is optional and is normally not used. Specifying the.f fields can access all of the fields of a counter.However, it is possible to use /b to single out a bit inthe .PRE or .ACC fields (which are words). ForCounter files, the bit number must be 0 - 15 decimal.Examples:C5:0.ACCC5:3.OVC5:1.PREControl File ItemsR[n]:e[.f][/b]n represents the file number and is optional. If notspecified, it is assumed to be 6. If specified, the filenumber must be 3 - 999 decimal.e specifies the element number (three words perelement) within the Control file. It must be 3 - 999decimal..f identifies one of the valid Control fields. The validfields for Control files are listed in the table. If .f isomitted, it is assumed to be the word containing thestatus bits.b is optional and is normally not used. Specifying the.f fields can access all of the fields of a Control file.However, it is possible to use /b to single out a bit inthe .LEN or .POS fields (which are words). Ifspecified, it indicates the bit (0 - 15 decimal).Examples:R6:0.LENR6:3.EMR6:1.POSABDHPLUS DAServer User’s Guide

42 Chapter 3Integer File ItemsN[n]:e[/b]n represents the file number and is optional. If notspecified, it is assumed to be 7. If specified, the filenumber must be 3 - 999 decimal.e specifies the element number within the Integer file. Itmust be 0 - 999 decimal.b is optional. If specified, it indicates the bit (0 - 15decimal).Examples:N7:0N7:0/15N7:3Floating Point File ItemsF[n]:en represents the file number and is optional. If notspecified, it is assumed to be 8. If specified, the filenumber must be 3 - 999 decimal.e specifies the element number within the Floating Pointfile. It must be 0 - 999 decimal.Examples:F8:0F8:3ASCII File ItemsAn:e[/b]An:x-yn represents the file number (NOT optional) and must be3 - 999 decimal.e specifies the element number within the ASCII file. Itmust be 0 - 999 decimal. Each element in an ASCII filecontains two ASCII characters.b is optional. If specified, it indicates the bit (0 - 15decimal).x and y also specify element numbers. In this form, theitem is an ASCII string occupying element x throughelement y. Each element contains two ASCII characters:the first character is the high-order byte and the second isthe low-order, and so on.Note If reading only one word as a two-character string, the range must be "xx."For example, A20:3-3.ABDHPLUS DAServer User’s Guide

Item Names 43Examples:A20:3A10:0/0A9:0-19(40-character ASCII string)BCD File ItemsDn:e[/b]n represents the file number (NOT optional) and mustbe 3 - 999 decimal.e specifies the element number within the BCD file. Itmust be 0 - 999 decimal. Each element in a BCD filecontains a number between 0 - 9999.b is optional. If specified, it indicates the bit (0 - 15decimal).Examples:D20:3D10:0/3ASCII String Section ItemsSTn:e[.f]n represents the file number (NOT optional) and mustbe 3- 999 decimal.e specifies the element number within the String file.It must be 0 - 779 decimal. Each element in a Stringfile contains an ASCII string with a maximum lengthof 82 characters..f identifies the following ASCII string field: .LEN. If.f is omitted, it is assumed to be the string.Examples:ST9:0ST9:700ST9:700.LENABDHPLUS DAServer User’s Guide

44 Chapter 3Block Transfer Section ItemsBTn:e[.f][/b] n represents the file number (NOT optional) and must be 3- 999 decimal.e specifies the element number (three words per element)within the Block Transfer file (0 - 999 decimal)..f identifies one of the valid Block Transfer fields. Thevalid fields for Block Transfer items are listed in the table.If .f is omitted, it is assumed to be the word containing thestatus bits.b is optional and is normally not used. Specifying the .ffields can access all of the fields of a Block Transfer.However, it is possible to use /b to single out a bit in the.FILE or .ELEM fields (which are words). For BlockTransfer files, the bit number must be 0 - 15 decimal.Note Block Transfer files are read only.Examples:BT9:0.ENBT9:3.RLENBT9:3.FILEPID Section ItemsPDn:e.f[/b]n represents the file number (NOT optional) and must be3 - 999 decimal.e specifies the element number within the PID file. Itmust be 0 - 398 decimal..f identifies one of the valid PID fields. The valid fieldsfor PID files are listed in the table. If PID field .ADDR isneeded, use .ADRE for element and .ADRF for file.b is optional and is normally not used. All of the fields ofa PID can be accessed by specifying the .f fields. Ifspecified, it indicates the bit (0 - 15 decimal).WARNING! Access to PID files may degrade the DAServer's performancedue to the extreme size of the PID element (82 words each). If accessing only afew PIDs at a time, performance will not be greatly affected. If accessing a fewfields of many PIDs at once, it may be faster to move the needed fields to anintermediate file (Floating Point or Binary) and let the DAServer access theintermediate files.Examples:PD9:2.SPPD9:3.OLHPD9:0.INIABDHPLUS DAServer User’s Guide

Item Names 45SFC Status Section ItemsSCn:e[.f][/b]n represents the file number (NOT optional) and mustbe 3 - 999 decimal.e specifies the element number within the SFC Statusfile. It must be 0 - 999 decimal..f identifies one of the valid SFC fields. The validfields for SFC files are listed in the table.b is optional and is normally not used. Specifying the.f fields can access all of the fields of an SFC. For SFCStatus items, the bit number must be 0 - 15 decimal.Examples:SC9:0SC9:0.PRESC9:0.SASLC 500 Item NamingThe general format of item names for data from SLC 500 controllers matchesthe naming convention used by the programming software. In the followingformat, the parts of the name shown in square brackets ([]) are optional.[$] X [file #] : element [.field] [/bit]$ – Purely optional.X – Identifies the file type.file # – Identifies the file number. File number must be 0 - 255 decimal. File 0must be Output, file 1 must be Input, and file 2 must be Status.element – Element number within the file. For Input and Output files it mustbe 0 - 30 decimal. All other file types, it must be 0 - 255 decimal..field – Valid only for Counter, Timer, and Control files; see table above./bit – Valid for all file types except ASCII String and Floating Point. Must be 0- 15 decimal.The following table summarizes the valid file types, the default file number foreach type, and the .fields allowed (if any):XFile TypeDefault File# .fieldsO Output* 0 N/AI Input* 1 N/AS Status 2 N/AB Binary 3 N/AT Timer 4 .PRE .ACC .EN .TT .DNC Counter 5 .PRE .ACC .CU .CD.DN .OV .UN .UAABDHPLUS DAServer User’s Guide

46 Chapter 3XFile TypeDefault File# .fieldsR Control 6 .LEN .POS .EN .DN .ER.UL .IN .FDN Integer 7 N/AF Floating Point* 8 N/AA ASCII* None N/AST ASCII String* None N/A*Available only on certain SL-500 models. Check the Processor Manual for the model being used. If the FloatingPoint file type is not supported, file 8 is reserved and unusable.Output File ItemsO[n]:e[/b]n represents the file number and is optional. Ifspecified, it must be 0 (zero).e indicates the element number in the file.b specifies the bit (0 - 15 decimal). /b may be omittedif necessary to treat the I/O group as a numeric value.Note The elements in I/O modules are sequentially mapped into a memorytable and are different from the item names in the PLC programming software.Refer to the following "Addressing SLC I/O Modules."Examples:O0:0/0$O:2/15O:3 4BCD (for 16-bit 7-segment display)Input File ItemsI[n]:e[/b]n represents the file number and is optional. Ifspecified, it must be 1.e indicates the element number in the file.b specifies the bit (0 - 15 decimal). /b may be omittedif necessary to treat the I/O group as a numeric value.Note The elements in I/O modules are sequentially mapped into a memorytable and are different from the item names in the PLC programming software.Refer to the following "Addressing SLC I/O Modules."Examples:I1:0/0I:2/15I:3 4BCD (for 16-bit thumbwheel input)ABDHPLUS DAServer User’s Guide

Item Names 47Addressing SLC I/O ModulesThe elements (words) in I/O modules are mapped into a memory table. If theAnalog I/O modules are being used, then the point naming will differ from thepoint naming in the programming software. The DAServer item name must becomputed from the sum total of words used by the previous input or outputblocks. The operator can use the programming software Data Monitor to lookat the memory map of the I file or O file to verify your address. If you are notsure of the address, or if the PLC configuration is likely to change, copy thepoints in question to the N table or B table and access the data from there.The naming conventions used in the Allen-Bradley programming software arenot supported by the Allen-Bradley Ethernet Direct DAServer. The addressingconvention is similar to that of the PLC-5 family processors. To derive thecorrect address for each I/O point, see the following Diagram System. Also seethe following topics, Label I/O Modules with "Word Counts," SequentiallyNumber the Input Modules, and Sequentially Number the Output Modules, tocomplete addressing the SLC I/O modules.Diagram SystemAddressing of the I/O points begins by drawing a schematic of the system. Thefollowing figure is a diagram of the SLC-5/02 system.The far left unit is the power supply. From left to right, the modules are:1747-L524 SLC-5/02 Module Processor1746-IA8 8-point 120VAC input module1746-OA16 16-point 120VAC output module1746-IA16 16-point 120VAC input module1746-NI4 4-point 20mA analog input module1746-NO4I 4-point 20mA analog output module1746-0A8 8-point 120VAC input module1746-IB32 32-point DC input moduleABDHPLUS DAServer User’s Guide

48 Chapter 3Label I/O Modules with "Word Counts"The address of any point within the I/O datatable space, in an SLC processor, isthe sum of the words occupied by previous modules (to the left in the rack) ofthe same type. Therefore, to determine the correct address for any particularpoint in the I/O datatable, one must know the number of words each modulewill consume. Refer to the following list:Number ofWords Module0 1747-L524 SLC-5/02 Module Processor1 1746-IA8 8-point 120VAC input module1 1746-OA16 16-point 120VAC output module1 1746-IA16 16-point 120VAC input module4 1746-NI4 4-point 20mA analog input module4 1746-NO4I 4-point 20mA analog output module1 1746-0A8 8-point 120VAC input module2 1746-IB32 32-point DC input moduleNote In the preceding table, the minimum number of words which can beconsumed by a module is 1 (16-bits). This is due to the memory scheme of allAllen-Bradley processors.Sequentially Number the Input ModulesIn the following I/O diagram, the first input module's addressing should startwith "I:0." Previously noted, this module consumes one datatable word.Therefore, the addressing of the next INPUT module encounter, moving fromleft to right, will begin with "I:1," regardless of the module's physical location.Sequentially Number the Output ModulesIn the following I/O diagram, the first output card encountered is the OA16.Although it is not in the first slot, its address will be "O:0" ('OHH, colonZERO"). This module consumes one datatable word. Therefore, the addressingof the next OUTPUT module; moving from left to right, will begin with "O:1,"regardless of the module's physical location.ABDHPLUS DAServer User’s Guide

Item Names 49I/O DiagramStatus File ItemsS[n]:e[/b]n represents the file number and is optional. If specified,it must be 2.e indicates the element number in the file.b is optional. If specified, it indicates the bit (0 - 15decimal).Note Refer to the SLC-500 Family Processor Manual (Allen-BradleyPublication) for a complete description of Status file information.Examples:S2:6 (major error fault)S2:13 (math register)S:1/5(forces enabled)ABDHPLUS DAServer User’s Guide

50 Chapter 3Binary File ItemsB[n]:e/b orB[n]/mn represents the file number and is optional. If notspecified, it is assumed to be 3. If specified, the filenumber must be 3 or 9 - 255 decimal.e specifies the element (word) number within the Binaryfile. It must be 0 - 255 decimal.b specifies the bit number within the word. In the firstform (where :e is present), the bit number must be 0 - 15decimal.m also represents the bit number. However, in the secondform, no word numbers are specified and the bit numbermay be 0 - 4095.Examples:B:33B:6/4 (same bit as B/100)B3/4095 (same bit as B:255/15)Timer File ItemsT[n]:e[.f][/b]n represents the file number and is optional. If notspecified, it is assumed to be 4. If specified, the filenumber must be 4 or 9 - 255 decimal.e specifies the element number (three words perelement) within the Timer file. It must be 0 - 255decimal..f identifies one of the valid Timer fields. The validfields for Timer Files are listed in the table. If .f isomitted, it is assumed to be the word containing thestatus bits.b is optional and is normally not used. All of the fieldsof a timer can be accessed by specifying the .f fields.However, it is possible to use /b to single out a bit inthe .PRE or .ACC fields (which are words). The bitnumber must be 0 - 15 decimal.Examples:T4:0.ACCT4:3.DNT4:1.PREABDHPLUS DAServer User’s Guide

Item Names 51Counter File ItemsC[n]:e[.f][/b]n represents the file number and is optional. If notspecified, it is assumed to be 5. If specified, the filenumber must be 5 or 9 - 255 decimal.e specifies the element number (three words perelement) within the Counter file. It must be 0 - 255decimal..f identifies one of the valid Counter fields. The validfields for the Counter Files are listed in the table. If .f isomitted, it is assumed to be the word containing thestatus bits.b is optional and is normally not used. Specifying the .ffields can access all of the fields of a counter. However,it is possible to use /b to single out a bit in the .PRE or.ACC fields (which are words). The bit number mustbe 0 - 15 decimal.Examples:C5:0.ACCC5:3.OVC5:1.PREControl File ItemsR[n]:e[.f][/b]n represents the file number and is optional. If notspecified, it is assumed to be 6. If specified, the filenumber must be 6 or 9 - 255 decimal.e specifies the element number (three words per element)within the Control file. It must be 0 - 255 decimal..f identifies one of the valid Control fields. The validfields for the Control files are listed in the table. If .f isomitted, it is assumed to be the word containing thestatus bits.b is optional and is normally not used. All of the fields ofa Control file can be accessed by specifying the .f fields.However, it is possible to use /b to single out a bit in the.LEN or .POS fields (which are words). The bit numbermust be 0 - 15 decimal.Examples:R6:0.LENR6:3.ENR6:1.POSABDHPLUS DAServer User’s Guide

52 Chapter 3Integer File ItemsN[n]:e[/b]n represents the file number and is optional. If notspecified, it is assumed to be 7. If specified, the filenumber must be 7 or 9 - 255 decimal.e specifies the element number within the Integer file. Itmust be 0 - 255 decimal.b is optional. If specified, it indicates the bit (0 - 15decimal).Examples:N7:0N7:0/15N7:3Floating Point File ItemsF[n]:en represents the file number and is optional. If notspecified, it is assumed to be 8. If specified, the filenumber must be 8 - 255 decimal.e specifies the element number within the Floating Pointfile. It must be 0 - 255 decimal.Examples:F8:0F8:3ASCII File ItemsAn:e[/b]n represents the file number (NOT optional) and mustbe 9 - 255 decimal.e specifies the element number within the ASCII file.It must be 0 - 255 decimal. Each element in an ASCIIfile contains two ASCII characters.b is optional. If specified, it indicates bit (0 - 15decimal).Examples:A20:3A10:0/0ABDHPLUS DAServer User’s Guide

Item Names 53ASCII String Section ItemsSTn:en represents the file number (NOT optional) and mustbe 9 - 255 decimal.e specifies the element number within the String file. Itmust be 0 - 255 decimal. Each element in a String filecontains an ASCII string with a maximum length of 78characters.Examples:ST9:0ST9:200DAServer Standard System ItemsSystem items supply DAServer users with easy access to DAServer status anddiagnostics information. They are treated just like ordinary items with respectto the client. However, in most cases these items are not directly acquired viathe communications layer. System item values are usually generated throughinternal calculations, measurements, and the tracking of the DAS Engine.No DAServer-specific system items are provided in this ABDHPLUSDAServer.System items, like ordinary items, are defined by the following properties:• Group (client group/OPC group)The arbitrary collection of items, not correlated.• Hierarchical location (link name/OPC path. The hierarchical node sectionof the fully qualified OPC item ID.)The device the item is attached to.• Device group (OPC access path/topic, or a Scan Group on a hierarchicalbranch.)The collection of items on the same physical location with the sameprotocol update rate.Example:To check the status of an external device, the reference might be:ABDHPLUS.ABPLC1.$SYS$StatusNote This syntax does not refer to the access path/device group. As long asthe data requested is from the same external device, the value will always bethe same.ABDHPLUS DAServer User’s Guide

54 Chapter 3Note For DDE/SuiteLink clients, $SYS$Status always comes from the leaflevel of a DAServer hierarchy branch, which is the destination PLC node. ForOPC clients, $SYS$Status can be accessed at all hierarchy levels. $SYS$Statusat the root level of the whole hierarchy tree is always good, as it represents thequality status of the local computer itself. Hence, for practical application,OPC clients should reference $SYS$Status at any hierarchy levels other thanthe root.In the ArchestrA context, the device group plays the most important role ofidentifying the scope of any item (the device group defines the hierarchicallocation implicitly when using globally unique device-group names, which isrequired for DDE/SuiteLink compatibility).All system items follow the same naming convention:• All system items start with $SYS$.• The DAS Engine scans and parses the name for system items. Parsing ofthe name is case-insensitive.All system items can be accessed through subscriptions to a device group.However, while some system items return data for that device group, others areserver-wide.DAServer Global System ItemThe following system item refers to specific information regarding a globalcondition of the DAServer.System Item Name$SYS$LicensedType/AccessRights Description ValuesBoolean/ReadThe Binary status indication of theexistence of a valid license for theDAServer.If FALSE, this item causes the DAServerto stop updating existing tags, to refuseactivation of new tags, and to reject writerequests as well as setting quality for allitems to BAD.If TRUE, the DAServer functions asconfigured. All instances have the samevalue.RANGE: 0, 11: Valid license exists.0: No valid license exists.DAServer Device-Specific System ItemsThe following system items refer to specific information regarding thedevice(s) the DAServer is connected to.ABDHPLUS DAServer User’s Guide

Item Names 55System Item Name(Type)$SYS$Status$SYS$ErrorCode$SYS$ErrorTextType/AccessRights Description ValuesBoolean/ReadLongint/ReadString/ReadThe Binary status indication of theconnection state to the device (hierarchylevel) the item is attached to.The device group (OPC accesspath/topic) does not affect the value. Thestatus can be good even if individualitems have errors.For DDE/SuiteLink clients, $SYS$Statusalways comes from the leaf level of aDAServer hierarchy branch, which is thedestination PLC node.For OPC clients, $SYS$Status can beaccessed at all hierarchy levels.$SYS$Status at the root level of thewhole hierarchy tree is always good, as itrepresents the quality status of the localcomputer itself. Hence, for practicalapplication, OPC clients shouldreference $SYS$Status at any hierarchylevels other than the root.Detailed error code of thecommunications state to the device.The device group (OPC accesspath/topic) does not affect the value.Detailed error string of thecommunications state of the device.The device group (OPC accesspath/topic) does not affect the value.RANGE: 0, 11: DAServer connectionto the device is intact.0: Error communicatingwith the device.>= 0: Good status (0 isthe default state –connected.>0: is some device statesuch as, connecting,initializing, and so on.

56 Chapter 3System Item Name(Type)$SYS$StoreSettingsType/AccessRights Description ValuesInteger/Read/WriteUsed to make the temporary updateinterval changes via the$SYS$UpdateInterval item permanent.If the client pokes a value of 1 into thissystem item, the currently set updateinterval is written to the server’sconfiguration file.The value of this system item clears to 0after being set, if the configuration filewrite is successful. If the write fails, thenthe value is set to -1.If the update interval has been changedvia the $SYS$UpdateInterval item andthis item is not poked to 1, the DAServeruses the original update interval for thattopic the next time it is started.Reading the item always provides 0.Read/Write values are persisted only ifthe user sets this system item. The valuesother than this persist only for the life ofthe DAServer.RANGE: -1, 0, 1-1: Error occurred duringsaving the configurationfile.0: Read value always ifstatus is OK.1: Persist settings(cleared immediately).DAServer Device-Group-Specific System ItemsThe following system items refer to specific information regarding devicegroups that have been configured in the DAServer.System Item Name(Type)$SYS$UpdateInterval$SYS$MaxIntervalType/AccessRights Description ValuesDWord/Read/WriteDWord/ReadUsed to access the currently set updateinterval. It is the current update intervalof the device group in milliseconds. Aclient can poke new values into this item.The value of zero indicates that no nonsystemitems on that topic are updated(data for these items are not acquiredfrom the device).Used to access the currently measuredmaximum update interval inmilliseconds of all items of thecorresponding device group. This item isread only. The value of the slowest itemis displayed.Range: 1…21474836470: Topic inactive, noitems are updated. Dataacquisition is stopped.>0: Expected updatedinterval for the set of allitems in the devicegroup.Range: 0…21474836470: If update interval is 0or if the status is false.>0: Measured updateinterval.ABDHPLUS DAServer User’s Guide

Item Names 57System Item Name(Type)$SYS$WriteComplete$SYS$ReadComplete$SYS$ItemCount$SYS$ActiveItemCountType/AccessRights Description ValuesInteger/Read/WriteInteger/Read/WriteDWord/ReadDWord/ReadUsed to access the state of pending Writeactivities on the corresponding devicegroup. On device group creation (addingitems to an OPC group) the value of thissystem item is initially 1, indicating allWrite activities are complete – no pokesare pending.If values are poked into any items of thedevice group, the value of this itemchanges to 0, indicating Write activity iscurrently in progress. If the server hascompleted all Write activities, the valueof this item changes to 1 if all pokes weresuccessful or to -1 if at least one poke hasfailed.If the value of this item is not zero, theclient can poke 1 or -1 to it (poke a 1 toclear errors or a -1 to test a client reactionon Write errors). If the value of this itemis zero, it cannot be poked.Used to access the state of initial Readson all items in the corresponding devicegroup. The value is 1 if all active items ina device group have been read at leastonce.If at least one item in the device group isactivated, this item changes to 0. Itchanges to 1 if all items have been readsuccessfully or to -1 if at least one itemhas a non-good quality.Poking a 0 to this item resets the internalRead states of all items in this devicegroup. This resets this item to 0.If all items are read again after this poke,this item changes back to 1 or -1.Used to access the number of items in thecorresponding device group. This item isread-only.Used to access the number of activeitems in the corresponding device group.This item is read-only.Range: -1, 0, 11: Write complete (noWrites are pending –initial state).0: Writes are pending.-1: Writes completedwith errors.Range: -1, 0, 11: Read complete (allvalues have been read).0: Not all values havebeen read.-1: All values have beenread but some have anon-good quality.Range: 0…2147483647>=0: Number of activeitems.Range: 0…2147483647>=0: Number of activeitems.ABDHPLUS DAServer User’s Guide

58 Chapter 3System Item Name(Type)$SYS$ErrorCount$SYS$PollNowType/AccessRights Description ValuesDWord/ReadBoolean/Read/WriteUsed to access the number of all items(active and inactive) that have errors(non-good OPC quality) in thecorresponding topic. If thecommunications status of a device groupis bad, all items have errors. This item isread-only.Poking a 1 to this item forces all items inthe corresponding device group to beread immediately (all messages in thisdevice group become due). This is usefulif you want to force to get the newestvalues from the device, regardless of itsupdate interval. This also works ondevice groups with a zero update interval(manual protocol triggering).Range: 0…2147483647>=0: Number of all items(active and inactive) witherrors.Range: 0, 1Generic OPC SyntaxA DAServer serves as a container for OPC Groups, which provide themechanism for containing and logically organizing OPC items. Within eachOPC Group, an OPC-compliant client can register OPC items, which representconnections to data sources in the field device. In other words, all access toOPC items is maintained through the OPC Group.The fully qualified name for an OPC item is called the Item ID (equivalent toItem Name). The syntax for specifying a unique Item ID is DAServerdependent.In OPC data acquisition DAServers, the syntax can be as follows:AREA10.VESSEL1.TIC1.PLC.N7:11Where:Each component (delimited by a period) represents a branch or leaf of thefield device’s hierarchy.In this example:• PLC is the name of the target PLC.• N7:11 is the specific data point (Item) desired.An item is typically a single value such as an analog, digital, or string value.Where Item ID describes the syntax for defining the desired data point, OPCprovides for another parameter, called Access Path, that defines optionalspecifications for obtaining that data. The following table shows the OPC DataAccess syntax.ABDHPLUS DAServer User’s Guide

Item Names 59ConfigurationAdapter –> PLC5/SLC500Adapter –> 1785KA5 –> SLC500Adapter –> 1785KE –> PLC5Syntax........Adapter –> 1785KA1–> 1785KA2 –> PLC5 ....In DAServers, Access Paths are equivalent to Device Groups; it is thisparameter that is used to define the update interval between the DAServer andthe field device for accessing the values of data points in the PLC.ABDHPLUS DAServer User’s Guide

Troubleshooting 61CHAPTER 4TroubleshootingThis chapter describes the troubleshooting tools that can be used to deal withthe ABDHPLUS DAServer problems you may encounter.The DAServer Manager provides access to diagnostics and other statisticaldata, and the Log Viewer provides access to event messages logged during theoperation of a DAServer. Also, your client (for example, InTouch) can monitorconnectivity with the PLC through the $SYS$Status item. Use these toolstogether with the information in this section to troubleshoot your ABDHPLUSDAServer.Note In order to determine the version of your DAServer, perform thefollowing steps. Search for DASABDHPLUS.dll, right-click on the FileName, select Properties on the shortcut menu, and select the Version tab onthe Properties dialog box. The version of your DAServer is listed under FileVersion.Contents• Monitoring Connectivity Status with the PLC• Monitoring the Status of DAS Conversations• Error Messages, Codes, and ConditionsMonitoring Connectivity Status with the PLCThe built-in discrete item, $SYS$Status, can be used to monitor the status ofcommunications with the PLC. This item is set to the following:0 (zero) when communications with the PLC fails.1 (one) when communications is successful.Note For DDE/SuiteLink clients, $SYS$Status always comes from the leaflevel of a DAServer hierarchy branch, which is the destination PLC node. ForOPC clients, $SYS$Status can be accessed at all hierarchy levels. $SYS$Statusat the root level of the whole hierarchy tree is always good, as it represents thequality status of the local computer itself. Hence, for practical application,OPC clients should reference $SYS$Status at any hierarchy levels other thanthe root.ABDHPLUS DAServer User’s Guide

62 Chapter 4Enter the following DDE reference formula in the appropriate place in yourclient:=DASABDHPLUS|ABPLC!$SYS$Statuswhere:DASABDHPLUS is the name of the DAServer application.ABPLCis the exact device group defined in the DAServerfor the PLC.$SYS$Status is the discrete item used to monitor the status ofconnectivity with the PLC.Enter the following OPC item reference syntax when adding the item in yourOPC client:YourOPCAccessPath.$SYS$Statuswhere:YourOPCAccessPath is the assembly of hierarchy node names leadingto a specific controller device.$SYS$Status is the discrete item used to monitor the status ofconnectivity with the controller device.Note In the case of a PLC disconnect, the DAServer will retry three timesbefore entering into slow poll mode. In the case of reply time-out, theDAServer will go into slow poll mode immediately.Monitoring the Status of DAS ConversationsThe InTouch WindowViewer supports built-in topic names, calledDDEStatus and IOStatus, that can be used to monitor the status of specificDAS conversations. For example, let us assume that WindowViewer (VIEW)is communicating with the ABDHPLUS DAServer to a PLC that has beendefined in the DAServer with the topic name ABPLC. The discrete items,DDEStatus and IOStatus, are set to 0 when this DAS conversation failed, andto 1 when this DAS conversation is successful.Using DDEStatus and IOStatus in ExcelThe status of communications between the PLC and InTouch can be read intoExcel by entering the following DDE reference formula in a cell on aspreadsheet:=view|DDEStatus!ABPLCorABDHPLUS DAServer User’s Guide

Troubleshooting 63=view|IOStatus!ABPLCwhere:viewis the name of the InTouch application.[DDE][IO] Status is the built-in topic name used to monitor the statusof communications between the DAServer andInTouch.ABPLCis the exact topic name defined in the server for thePLC.Reading Values from the DAServer into ExcelValues may be read directly into Excel spreadsheets from the DAServer byentering a DDE formula into a cell using the following format:=applicationname|topicname!itemnameExample formula:=DASABDHPLUS|ABPLC!'N7:0'where:DASABDHPLUS is the name of the DAServer application.ABPLC is the exact device group name defined in theDAServer for the PLC.N7:0 is the actual location in the PLC that contains the datavalue. This is the item name.In this example, each time the value of N7:0 changes in the PLC, theDAServer will automatically send the new value to the cell containing theformula in Excel.Note Refer to the Microsoft Excel manual for complete details on enteringRemote Reference formulas for cells.Writing Values to the DAServer from ExcelValues may be written to the DAServer from Microsoft Excel by creating anExcel macro that uses the POKE command. The proper command is entered inExcel as follows:channel=INITIATE("applicationname","topicname")=POKE(channel,"itemname", Data_Reference)=TERMINATE (channel)=RETURN()The following describes each of the above POKE macro statements:channel=INITIATE("applicationname","topicname")ABDHPLUS DAServer User’s Guide

64 Chapter 4• Opens a channel to a specific topic name (defined in the DAServer) ina particular application name (the executable name less the .exe).• Assigns the number of that opened channel to channel.Note By using the channel=INITIATE statement, the word channel must beused in the =POKE statement instead of the actual cell reference. The"application name" and "topic name" portions of the formula must beenclosed in quotation marks.=POKE(channel,"itemname", Data_Reference)• POKEs the value contained in the Data_Reference to the specifieditem name (actual location in the PLC), via the channel numberreturned by the previously executed INITIATE function.• Data_Reference is the row/column ID of the cell containing the datavalue.=TERMINATE(channel)• Closes the channel at the end of the macro.• Some applications have a limited number of channels; therefore, theyshould be closed when finished.• Channel is the channel number returned by the previously executedINITIATE function.=RETURN()• Marks the end of the macro.Note Refer to the .xlm sample Excel poke macro provided on the DAServerCD. Also refer to the Microsoft Excel manual for complete details on enteringRemote Reference formulas for cells.Error Messages, Codes, and ConditionsDAServer error messages, controller-specific error messages, ABDHPLUSDAServer error codes, and error conditions generated by the Data HighwayPlus are supported. Use the Log Flag data to customize the type of messageslogged to the Log Viewer. See the Log Viewer online documentation for moreinformation about using log flags.To troubleshoot DAServer problems, use the following error messagestogether with the DAServer Manager Diagnostics root data.DAServer Error MessagesThe following table lists all the generic-DAServer and ABDHPLUS-DAServer-specific error messages.ABDHPLUS DAServer User’s Guide

Troubleshooting 65Error Message Explanation Possible Cause Solution Log FlagUnable to read Firmwarefor card from Card failure. Cannot readAdapter card boot_codeat addresses 0-3xCannot get driverinformation/status datafrom AB1784KT.SYSThe AB1784KT.SYSdevice driver is notrunning. GetLastError= forCard failure during RAMtest. Timeout waiting fora response. (offset0x7FF!=1)Card failure of Dual-PortRAMCard failure of both CTCTimer and CounterCard failure during SerialIO test. Timeout waitingfor a response.Protocol firmwaredownload block too largeSS NT kernel devicedriver not present. SeeEvent Viewer forpossible reasonBoard not acceptingreset, shows busyThe value of theparameter, "FirmwarePath," is incorrect.The reading of Byteoffset into the adaptercard’s memory failed.The reading of the driverinfo failed.The AB1784KT driver isnot running.The driver verifies theintegrity of the RAMused for its internalvariable storage, bytesting a portion of theRAM after transmissionof each packet.The integrity of data inthe dual-port RAM isprotected by the parityerror detection in thedual-port hardware.A problem isencountered in the card’stimer or counter.There is a problemencountered in the SerialIO of the card.An error occurs in thefirmware file.An error occurred duringthe start-up of the devicedriver.There is a problem in theSST card.An incorrect pathwas enteredduring theconfiguration.There is a faultycard or a loosecontact.The driver maynot be running.The firmware filemay be corrupted.The device drivermay not beinstalled properly.Deactivate theserver and re-enterthe correct path inthe Firmware Pathbox of theConfigurationdialog box.Replace the card.Restart the servercomputer.Restart the servercomputer.Restart the servercomputer.Restart the servercomputer.Restart the servercomputer.Restart the servercomputer.Replace thefirmware file with anew one.DASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailReinstall the server. DASProtFailThe card may needto be replaced.DASProtFailABDHPLUS DAServer User’s Guide

66 Chapter 4Error Message Explanation Possible Cause Solution Log FlagConnection Timeout -Failed to obtain a QueueBox.Free Qbox called forQbox# whenpacket received butfailed to read data bufferRunt (too short)unsolicited messagepacket received onAdapter Card Unsolicited messagepacket (from node) for unadviseditem received on AdapterCard Could not find PLC nodewhen creating messageERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Anaddress field has anillegal value - check theTopic Configurationdialog, the block sizesmay be too large or thePLC type may beincorrect.Unable to get a freeQueue Box.Unable to read data fromthe received message.The length of themessage is too short.Received message hasthe data for an Itemwhich is not advised.Failed to find the PLCnode from the hierarchyfrom the message.When doing this Read orWrite operation to theitem, the operation failedbecause an incorrectformat in a message wasfound. The reason forfailure is included in themessage.The MessageSend/Receivefunction is veryslow.Client may nothave advised theitem.When creating themessage for theitem, theDAServer cannotlocate the PLCnode. Possiblecorrupted or badCFG file.A bad requestmessage wasconstructed andsent.Increase the updateinterval.If the server is notable to recoverfrom this, check thenetworkconnection.If the server is notable to recoverfrom this, check thenetworkconnection.Advise theparticular itemthrough client.Check and correctthe CFG file.Make sure acorrectly formattedrequest messagewas constructedand sent. Make surethe PLC isconfiguredcorrectly.DASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 67Error Message Explanation Possible Cause Solution Log FlagERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Notenough address fieldsspecified - check theTopic Configurationdialog, the block sizesmay be too large or thePLC type may beincorrect.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Toomany address fieldsspecified - check theTopic Configurationdialog, the block sizesmay be too large or thePLC type may beincorrectERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error:Addressed symbol notfound - check the TopicConfiguration dialog, theblock sizes may be toolarge or the PLC typemay be incorrect.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error:Addressed symbol is >8or

68 Chapter 4Error Message Explanation Possible Cause Solution Log FlagERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Thisaddress does not exist inPLC - check Data Tabledefinition inside PLCand make sure ALLrequested points aredefined.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: One ormore points specifiedwithin this message donot exist in the PLC'sData Table - Pleasedefine, inside the PLC,the missing point(s).ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Cannotcomplete request; thesituation inside the PLCand/or bridge devices haschanged since thecommand started.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Data orFile is too large - thepacket the PLC is tryingto send back is too large -check the TopicConfiguration dialog.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause an incorrectformat in the messagewas found. The reasonfor failure is included inthe message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.Make sure acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 69Error Message Explanation Possible Cause Solution Log FlagERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error:Transaction size too largefor protocol - check theTopic Configurationdialog, the block sizesmay be too large or thePLC type may beincorrect.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: AccessDenied; improperprivilege - the PLC hasrefused us access to oneor more of the data pointsin this message - checkPRIVILEGE settingsinside PLC.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Aresource is not available -A programming terminalmay be connected to(communicating with)this PLC - pleasedisconnect theprogramming terminal.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error:Condition already exists;resource is alreadyavailable - a loss ofcommunicationssynchronization hasoccurred - if it continues,restart the DAServer.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.Writing to Read/Write operation toa PLC that isalready connectedto a programmingterminal.A bad requestmessage wasconstructed andsent.Make sure acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Disconnect theprogrammingterminal to the PLCand repeat theRead/Writeoperation.Make sure that acorrectly formattedrequest message isconstructed andsent. If errorcontinues, restartthe DAServer andrepeat theRead/Writeoperation.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

70 Chapter 4Error Message Explanation Possible Cause Solution Log FlagERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error:Command cannot beexecuted - the PLC hasrefused to execute thecommand we have sentto it - check the PLC typein the TopicConfiguration dialog.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error:Histogram Overflow -the PLC’s internal stackhas overflowed - checkPLC settings andhardware forconfiguration problemsERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: NoAccess - the PLC hasrefused us access to oneor more of the data pointsin this message - checkPRIVILEGE settingsinside the PLC.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: The datatype requested (seeFileType parameter) maynot match the data typefor the specified filenumber inside the PLC.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.A bad requestmessage wasconstructed andsent.The PLC settingwas incorrect.Cannot access thePLC.A bad requestmessage wasconstructed andsent.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure the PLCis configuredcorrectly.Make sure the PLCis configuredcorrectly. Repeatthe Read/Writeoperation aftercorrecting theconfiguration.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 71Error Message Explanation Possible Cause Solution Log FlagERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: The PLChas rejected the format ofour command - check theTopic Configurationdialog, the block sizesmay be too large or thePLC type may beincorrect.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: At leastone word of the PLC'sData Table we arerequesting with thismessage has beenmarked for deletion by aprogramming terminal -this is illegal.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Dataconversion error - checkPLC configuration andPLC type selection insidethe Topic Configurationdialog.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: RemoveI/O Scanner not able tocommunicate with 1771rack adapter - check PLCfor problems.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was found to beincorrect. The reason forfailure is included in themessage.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.Make sure acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

72 Chapter 4Error Message Explanation Possible Cause Solution Log FlagERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: RemoveI/O Adapter cannotcommunicate withmodule - check PLC forproblems.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: PLC'sremote I/O scanner isunable to update therequested data because ofa communicationproblem - check PLC forproblems.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error:Duplicated Label inMessage and/or PLC -you should check PLCsetup and TopicConfiguration for errors.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: File isopen; another node ownsit - a programmingterminal may beconnected to(communicating with)this PLC - pleasedisconnect theprogramming terminal.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause an incorrectformat in the messagewas found. The reasonfor failure is included inthe message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.A bad requestmessage wasconstructed andsent.Writing toRead/Writeoperation isperformed to aPLC that isalready connectedto a programmingterminal.Make sure acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Disconnect theprogrammingterminal to the PLCand repeat theRead/Writeoperation.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 73Error Message Explanation Possible Cause Solution Log FlagERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] encountered thefollowing error: Anothernode is the PLC programowner - a programmingterminal may beconnected to(communicating with)this PLC - pleasedisconnect theprogramming terminal.ERROR - When topic:[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:UnknownCommunication ErrorError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Destination node (PLC)is out of buffer space -Therefore, the PLC isrefusing to accept ourmessagesError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Remote node is notacknowledging (ACK)our requests for data - Isthe PLC on-line? Is thebridge device on-line?When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was found to beincorrect. The reason forfailure is included in themessage.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause an incorrectformat in the messagewas found. The reasonfor failure is included inthe message.Writing toRead/Writeoperation isperformed to aPLC that isalready connectedto a programmingterminal.A bad requestmessage wasconstructed andsent. This is a"catch all" errormessage.Cannotcommunicate withthe PLC correctly.Cannotcommunicate withthe PLC correctly.Disconnect theprogrammingterminal to the PLCand repeat theRead/Writeoperation.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.Make sure the PLCis configured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.Make sure the PLCis configured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

74 Chapter 4Error Message Explanation Possible Cause Solution Log FlagError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Duplicate token holderdetected - two stations onthe highway have thesame address (this isillegal)Error - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Local port isdisconnected - we maynot be connected(physically) to thehighway - check thecabling (wiredincorrectly?) and _ALL_connectors (loose?)Error - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Application layer timedout waiting for aresponseError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Duplicate node detected -two stations on thehighway have the sameaddress (this is illegal)When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was found to beincorrect. The reason forfailure is included in themessage.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.Cannotcommunicate withthe PLC correctly.Cannotcommunicate withthe PLC correctly.Cannotcommunicate withthe PLC correctly.Cannotcommunicate withthe PLC correctly.Make sure the PLCis configured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.Make sure the PLCis configured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.Make sure thatcabling is correctlyconnected.Make sure that thePLC is configuredand runningcorrectly andsuccessfully. Makesure that the PLC ison line and iscommunicatingwith the DAServer.Make sure the PLCis configured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 75Error Message Explanation Possible Cause Solution Log FlagError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Station is off-line - thePLC we are attempting tocontact is not on-lineError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Hardware fault - ahardware problem hasprevented messages frombeing sentError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:UnknownCommunication ErrorError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Illegal command orformat - check the TopicConfiguration dialog, theblock sizes may be toolarge, or the wrong PLCtype may be selectedWhen doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.Cannotcommunicate withthe PLC correctly.Cannotcommunicate withthe PLC correctly.Cannotcommunicate withthe PLC correctly.A bad requestmessage wasconstructed andsent.Make sure that allPLCs areconfigured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.Make sure all PLCsare configured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.Make sure that allhardware is runningand functioningcorrectly.Make sure all PLCsare configured andrunning correctlyand successfully.Make sure the PLCis on line and iscommunicatingwith the DAServer.Make sure that allhardware is runningand functioningcorrectly.Make sure that acorrectly formattedrequest message isconstructed andsent. Make sure thePLC is configuredcorrectly.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

76 Chapter 4Error Message Explanation Possible Cause Solution Log FlagError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Remote host will notcommunicate - PLC maynot be on-lineError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Remote host missing ordown - PLC may not beon-lineError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Remote host hardwarefault - PLC hasexperienced a hardwarefaultError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Addressing problem ormemory protection rungs(inside the PLC) haveprevented us fromretrieving the requestedinformationWhen doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.Cannotcommunicate withthe remote PLCcorrectly.Cannotcommunicate withthe remote PLCcorrectly.Cannotcommunicate withthe remote PLCcorrectly.Cannotcommunicate withthe remote PLCcorrectly.Make sure that allPLCs and allremote devices areconfigured andrunning correctlyand successfully.Make sure that allPLCs and allremote devices areconfigured andrunning correctlyand successfully.Make sure all PLCsand all remotedevices areconfigured andrunning correctlyand successfully.Make sure allhardware isworking correctly.Make sure that allPLCs and allremote devices areconfigured andrunning correctlyand successfully.Make sure allhardware isworking correctly.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 77Error Message Explanation Possible Cause Solution Log FlagError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Function disallowed dueto command protectioninside the PLC, or theposition of a hardwarekey on the PLCError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:PLC processor is inPROGRAM mode - itmust be in RUN modefor us to be able to gatherdataError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Compatibility mode filemissing orcommunication zoneproblem inside the PLCError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Remote node (PLC orBridge Device) cannotbuffer the command weare trying to send itWhen doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation failedbecause the format in themessage was incorrect.The reason for failure isincluded in the message.Cannotcommunicate withthe remote PLCcorrectly.Cannotcommunicate withthe remote PLCcorrectly.Cannotcommunicate withthe remote PLCcorrectly.Cannotcommunicate withthe remote PLCcorrectly.Make sure that allPLCs and allremote devices areconfigured andrunning correctlyand successfully.Make sure allhardware isworking correctly.Make sure all PLCsand all remotedevices areconfigured andrunning correctlyand successfully.Make sure that allhardware isworking correctly.Make sure that thePLC is not inProgram mode; itshould be in RUNmode.Make sure that allPLCs and allremote devices areconfigured andrunning correctlyand successfully.Make sure allhardware isworking correctly.Make sure all PLCsand all remotedevices areconfigured andrunning correctlyand successfully.Make sure allhardware isworking correctly.Make sure that thecorrect message hasbeen constructed tosend to the remotePLC.DASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

78 Chapter 4Error Message Explanation Possible Cause Solution Log FlagError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Remote node (PLC orBride Device) problemdue to download - adownload is most likelyin progress, please waituntil it is completeError - When topic[TopicName] tried toRead/Write [DESC of theitem] it encountered thefollowing error:STS=[sts error code]:Cannot executecommand due to activeIPBs inside the PLCA floating point valueread for Item: on Node: was NOT AVALID NUMBER(Negative Infinity),therefore, it wasconverted to +3.4e38A floating point valueread for Item: on Node: was NOT AVALID NUMBER(Positive Infinity),therefore, it wasconverted to +3.4e38A floating point valueread for Item: on Node: was NOT AVALID NUMBER(!NaN!), therefore, it wasconverted to +3.4e38When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.When doing this Read orWrite operation to theitem, the operation faileddue to an incorrectformat in the message.The reason for failure isincluded in the message.A bad negative floatingvalue was read from thePLC. The value waschanged by theDAServer to a knowngood value beforesending it to the client.A bad positive floatingvalue was read from thePLC. The DAServerchanged the value to aknown good value beforesending it to the client.A bad positive floatingvalue was read from thePLC. The DAServerchanged the value to aknown good value beforesending it to the client.Cannotcommunicate withthe remote PLCcorrectly.Cannotcommunicate withthe remote PLCcorrectly.Bad data was read. None.Bad data was read. None.Bad data was read. None.Make sure all PLCsand all remotedevices areconfigured andrunning correctlyand successfully.Make sure allhardware isworking correctly.Repeat theRead/Writeoperation after thedownload operationis completed.Make sure all PLCsand all remotedevices areconfigured andrunning correctlyand successfully.Make sure allhardware isworking correctly.DASProtFailDASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 79Error Message Explanation Possible Cause Solution Log FlagTerminating the class - Due tocard failed to initializeThe Item in Unsolicitedmessage is not advised:File Type=,File=, DataTable=Problem occurred duringthe initialization of thecard, which causes thetermination of thecreated object.Received Unsolicitedmessage has data forItem, which is notadvised.PLC-5 Error MessagesDriver may nothave startedproperly. Or,downloading ofthe firmware maycause the problem.Any client doesnot advise aparticular Item.There is apossibility of dataloss.Check the file pathof the firmware inthe configuration.Also check othererror messages,before this one, formore details.Advise the Itemthrough client.The error messages generated specifically for the PLC-5 family controllers arelisted in the following table.DASProtFailDASProtFailError Message Explanation Possible Cause Solution Log FlagItem notvalid, PLC does not havePID featureBINARY file numbermust be greater than 2TIMER file number mustbe greater than 2CONTROL file numbermust be greater than 2INTEGER file numbermust be greater than 2BCD file number mustbe greater than 2PID feature is notsupported for this PLC-5configuration.Incorrect format for thisitem. The Binary Item’sFile Number was smallerthan 3 for PLC-5.Incorrect format for theitem. The Timer Item’sFile Number was smallerthan 3 for PLC-5.The format for the item isincorrect. The ControlItem’s File Number wassmaller than 3 for PLC-5.Incorrect format for theitem. The Integer Item’sFile Number was smallerthan 3 for PLC-5.The format for the item isincorrect. The BCDItem’s File Number wassmaller than 3 for PLC-5.PLC-5configurationindicates that thePID feature is notsupported.The Binary Item’sFile Number mustbe 3 or larger.The Timer Item’sFile Number mustbe 3 or larger.The ControlItem’s FileNumber must be 3or larger.The Integer Item’sFile Number mustbe 3 or larger.The BCD Item’sFile Number mustbe 3 or larger.Select Support PIDfeature option forPLC-5, if the PLCsupports thefeature.Only access aBinary Item with aFile Number that isequal to 3 or larger.Only access aTimer Item with aFile Numberequaling to 3 orlarger.Only access aControl Item with aFile Number that isequal to 3 or larger.Only access anInteger Item with aFile Number that isequal to 3 or larger.Only access a BCDItem with a FileNumber equaling to3 or larger.DASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

80 Chapter 4Error Message Explanation Possible Cause Solution Log FlagPD file number must begreater than 2ST file number must begreater than 2BT file number must begreater than 2SC file number must begreater than 2Cannot write to fileBT[FileNumber]Incorrect format for theitem. The PID item’s FileNumber was smaller than3 for PLC-5.Incorrect format for theItem. The ST Item’s FileNumber was smaller than3 for PLC-5.Incorrect format for theItem. The BT Item’s FileNumber was smaller than3 for PLC-5.The format for the Itemis incorrect. The SCItem’s File Number wassmaller than 3 for PLC-5.Failed to write to a BTitem for PLC-5.SLC 500 Error MessagesThe PID Item’sFile Number mustbe 3 or larger.The ST Item’s FileNumber must be 3or larger.The BT Item’sFile Number mustbe 3 or larger.The ST Item’s FileNumber must be 3or larger.For PLC-5, Writeoperation to a BTitem is notpermitted.Only access a PIDItem with a FileNumber that isequal to 3 or larger.Only access an STItem with a FileNumber that isequal to 3 or larger.Only access a BTItem with a FileNumber equalingto 3 or larger.Only access an STItem with a FileNumber that isequal to 3 or larger.Do not attempt towrite to a BT itemfor PLC-5.The following table lists all the SLC-500-controller-specific error messages.DASProtFailDASProtFailDASProtFailDASProtFailDASProtFailError Message Explanation Possible Cause Solution Log FlagBINARY file numbermust be greater than 8TIMER file number mustbe greater than 8COUNTER file numbermust be greater than 8Incorrect format for thisitem. The Binary Item’sFile Number was smallerthan 9 for SLC 500.Incorrect format for theitem. The Timer Item’sFile Number was smallerthan 9 for SLC 500.The format for the item isincorrect. The CounterItem’s File Number wassmaller than 9 for SLC500.The Binary Item’sFile Number mustbe 9 or larger.The Timer Item’sFile Number mustbe 9 or larger.The CounterItem’s FileNumber must be 9or larger.Only access aBinary Item with avalid File Number.Only access aTimer Item with avalid File Number.Only access aCounter Item with avalid File Number.DASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

Troubleshooting 81Error Message Explanation Possible Cause Solution Log FlagCONTROL file numbermust be greater than 8INTEGER file numbermust be greater than 8Incorrect format for theitem. The Control Item’sFile Number was smallerthan 9 for SLC 500.Incorrect format for theitem. The Integer Item’sFile Number was smallerthan 9 for SLC 500.The ControlItem’s FileNumber must be 9or larger.The Integer Item’sFile Number mustbe 9 or larger.PLC-5 and SLC 500 Error MessagesOnly access aControl Item with avalid File Number.Only access anInteger Item with avalid File Number.The error messages listed in the following table pertain to both the PLC-5 andSLC 500 controllers.DASProtFailDASProtFailError Message Explanation Possible Cause Solution Log FlagFile numbers must bebetween 0 and 999OUTPUT file numbermust be 0INPUT file number mustbe 1STATUS file numbermust be 2Binary file, bit>15 andelement>0For PLC-5 and SLC 500:The format for the itemwas incorrect. The Item’sFile Number was out ofrange.For PLC-5 and SLC 500:Incorrect format for theitem. The Output Item’sFile Number was not 0.For PLC-5 and SLC 500:Incorrect format for theitem. The Input Item’sFile Number was not 1.For PLC-5 and SLC 500:Incorrect format for theitem. The Status Item’sFile Number was not 2.For PLC-5 and SLC 500:Incorrect format for theitem. The Binary Itemcontained an elementnumber, but its bitnumber was larger than15.A bad Item’s FileNumber is used.The Output Item’sFile Number mustbe 0.The Input Item’sFile Number mustbe 1.The Status Item’sFile Number mustbe 2.For PLC-5 andSLC 500: Thevalid format for aPLC-5 BinaryItem is:B[FileNumber]:[Element]/[Bit],where bit is from0 to 15. In thiscase, the bit fieldwas larger than15.Use a valid rangefor the Item’s FileNumber.Only access anOutput Item with aFile Number that isequal to 0.Only access anInput Item with aFile Number that isequal to 1.Only access aStatus Item with aFile Numberequaling to 2.Only access aBinary Item with avalid range.DASProtFailDASProtFailDASProtFailDASProtFailDASProtFailABDHPLUS DAServer User’s Guide

82 Chapter 4Error Message Explanation Possible Cause Solution Log FlagFLOATING POINT filenumber must be greaterthan 2FLOATING POINT filecannot have bit numberASCII file number mustbe greater than 2Unsupported file type[File Type][Sub-Element] not validfor type [FileType] files[Sub-Element] not validfor type [FileType]sectionAttempt to write readonly item in file[FileNumber] element[Element#] subelement[Sub-Element#] ignoredFor PLC-5 and SLC 500:The format for the item isincorrect. The FloatingPoint Item’s File Numberwas smaller than 3.For PLC-5 and SLC 500:Incorrect format for theitem. The Floating PointItem contained a bitnumber field.For PLC-5 and SLC 500:Incorrect format for theitem. The ASCII Item’sFile Number was smallerthan 3.For PLC-5 and SLC500: Incorrect format forthe item. An invalid Itemtype was used.For PLC-5 and SLC 500:Incorrect format for theitem. The Sub-element isnot valid for this FileType.For PLC-5 and SLC 500:Incorrect format for theitem. The Sub-element isnot valid for this section.For PLC-5 and SLC 500:the Write operation faileddue to an attempt to writeto a read-only item.The Floating PointItem’s FileNumber must be 3or larger.The Floating PointItem must notcontain a bitnumber field.The ASCII Item’sFile Number mustbe 3 or larger.There are no suchItem type names.There is a wrongItem format with awrong subelementtype.The Item format iswrong.An attempt towrite to a readonlyitem causedthe failure.ABDHPLUS DAServer Error CodesOnly access aFloating Point Itemwith a File Numberthat is equal to 3 orlarger.Only access aFloating Point Itemwithout a bitnumber field.Only access anASCII Item with aFile Number that isequal to 3 or larger.Use a valid Itemtype.Only access a validitem format with acorrect sub-elementtype.Use only a validitem format.Do not attempt aWrite operation to aread-only item.There are two server-specific error codes, as shown in the following table.These error codes, along with the error text, can be accessed through SystemItems.DASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailDASProtFailError CodeError Text-10001 PLC not connected-10002 PLC timeoutABDHPLUS DAServer User’s Guide

Troubleshooting 83Data Highway Plus Error ConditionsThe Data Highway Plus generates error conditions. These error conditions andthe server-specific strings are generated by the DAServer to the logger.Allen Bradley Error Code Logger Message Log FlagDHPERR_DP_FNC (0x20000001) Dual-port memory functionality test error DASProtFailDHPERR_RAM (0x20000002) Unknown random access memory test error DASProtFailDHPERR_RAM (0x20000003) Failure of Z80 RAM 0 DASProtFailDHPERR_RAM (0x20000004) Failure of dual-port RAM DASProtFailDHPERR_RAM (0x20000005) Failure of Z80 RAM 1 DASProtFailDHPERR_RAM01 (0x20000006) Failure of both Z80 RAM 0 and RAM 1 DASProtFailDHPERR_RAM1_DP (0x20000007) Failure of both RAM 1 and Dual-Port RAM DASProtFailDHPERR_CTC (0x20000008) Unknown counter timer circuit test error DASProtFailDHPERR_CTC_TMR (0x20000009) Failure of CTC timer module DASProtFailDHPERR_CTC_CNT (0x2000000A) Failure of CTC counter module DASProtFailDHPERR_CTC_TC (0x2000000B) Failure of both CTC timer and counter modules DASProtFailDHPERR_SIO (0x2000000C) Unknown serial input output test error DASProtFailDHPERR_SIO_INT (0x2000000D) Failure of CIO channel: no interrupt DASProtFailDHPERR_SIO_LOOP (0x2000000E) Failure of SIO channel A: Loopback failure DASProtFailDHPERR_PROT_LOAD (0x2000000F) Protocol file download error DASProtFailDHPERR_LOAD_BLK (0x20000010) Block too large error DASProtFailDHPERR_RAM_FULL (0x20000011) Z80 RAM too full for next block DASProtFailDHPERR_BD_WRITE (0x20000012) Cannot write to adapter card memory DASProtFailDHPERR_OPEN_LOADPCL(0x20000013)Cannot open file LOADPCL.BINDASProtFailDHPERR_OPEN_KLPCL (0x20000014) Cannot open file KLPCL.BIN DASProtFailDHPERR_OPEN_KLST0 (0x20000015) Cannot open file KLST0.BIN DASProtFailDHPERR_OPEN_KLST1 (0x20000016) Cannot open file KLST1.BIN DASProtFailDHPERR_OPEN_KLST2 (0x20000017) Cannot open file KLST2.BIN DASProtFailDHPERR_OPEN_PROT (0x20000018) Cannot open protocol file DASProtFailTIMEOUT_ERR (0x01) Timeout error DASProtFailCANCELLED_ERR (0x02) Cancelled error code DASProtFailABDHPLUS DAServer User’s Guide

84 Chapter 4ABDHPLUS DAServer User’s Guide

Reference 85CHAPTER 5ReferenceContents• DAServer Architecture• Component EnvironmentsDAServer ArchitectureDAServersNote DAServers are supported on Microsoft Windows 2000 and WindowsXP only. NetDDE protocol is not supported by the DAServers.This DAServer is a collection of components that work in concert to providecommunications access with hardware field devices. These componentsinclude:• DAServer Manager: This is the Microsoft Management Console (MMC)snap-in, which is part of the ArchestrA System Management Console(SMC) suite of utilities, supplied with the DAServer, that provides thenecessary user interface for diagnostics, configuration, and activation.• Client Plug-ins: These are the components that are added to a DAServerto enable communications with clients. Examples are: OPC,DDE/SuiteLink, etc.• DAS Engine: This is the library that contains all the common logic todrive data access.• Device Protocol: This is custom code provided by this DAServer todefine the communications with a particular device.A DAServer is comprised of three physical parts (see the following figure).They are the following:• Plug-in Component(s): This part is responsible for communicating withclients.• DAS Engine: This common component is used by all DAServers.• PLC Protocol Layer, DAServer-specific: This component is responsiblefor communicating with the hardware.ABDHPLUS DAServer User’s Guide

86 Chapter 5DAServer ArchitectureEach physical part of a DAServer is comprised of a set of .exe and/or .dllmodules. Wonderware provides the plug-ins and the DAS Engine. The DASToolkit user creates the PLC Protocol Layer (DAServer-specific) modules. Allthree sets of modules are required for a fully functioning DAServer.Plug-insPlug-ins provide a protocol translation function for device integration clients.Typical plug-ins communicate in DDE, SuiteLink, or OPC protocol, and serveas interfaces between their clients and the DAS Engine.Note Items of an array are not supported in the DDE/SL plug-in. These arraysare converted to HEXASCII strings, which provide legacy behavior forDAServers that support this in the DAServer-specific code.ABDHPLUS DAServer User’s Guide

Reference 87DAS EngineThe DAS Engine is a middleware component that exposes two sets of uniqueinterfaces, one for communicating with the plug-ins and one forcommunicating with the PLC Protocol Layer components.PLC Protocol LayerThe PLC Protocol Layer provides a protocol translation function for specifichardware such as ModBus, and serves as an interface between the DAS Engineand the hardware.Component EnvironmentsStand-alone DAServers have the following characteristics:• The DAS Engine is dynamically linked to the other DAServercomponents. In other words, a new DAS Engine (feature enhancement orbug fix) would not require relinking to the other components nor re-QA ofthose other components. When deployed to the system, the new DASEngine would attach to all existing DAServer components.• Newly deployed Plug-ins (feature enhancements or bug fixes) do notrequire relinking nor re-QA of associated components. Even new Plug-ins(for example, OPC Alarm & Events) would not require any developmentchanges to the other components, and therefore no relinking in a customerinstalledbase. In fact, it is feasible to implement new functionality in aplug-in to enhance the DAServer without involvement of the code of theother components.• DAServers can be configured in one stand-alone configuration utility(DAServer Manager), capable of displaying specific configuration pagesfor all DAServers. This utility allows browsing and editing of DAServerson different nodes.• The DAServer Manager diagnostics tool displays generic diagnosticobjects common to all DAServers, as well as DAServer-specific/DAServer-developer-defined diagnostic data.The DAServer data configuration format is XML. Any XML-enabled program(for example, XML Editor) can read this format.ABDHPLUS DAServer User’s Guide

88 Chapter 5ABDHPLUS DAServer User’s Guide

89IndexSymbols$45$SYS$Status 61.field 37, 45/bit 37, 45AABDHPLUS hierarchy 15, 21Access Path 58Access the settings for device groups 35Add PLC and Bridge-Module objects 27Application name 13ArchestrA System Management Console 20, 85ArchestrA.DASABDHPLUS.1 12ArchestrA.DASABDHPlus.1 18, 20Archive Configuration Set 35arrays 86BBaud Rate 25, 26Before 7Boolean item 14Bridge Module 11CCARD Objects 18, 22Client Plug-ins 85Communication Protocols 10Config Default Update Interval 33Configuration 15, 18Configuration node 35Configuration set 33Configuration Set Name 35Configure As Service 19, 22Configure default update intervals 33Configuring the DAServer 20Connection Timeout 24, 26Create or add device groups 32DDAS Engine 85DAS Toolkit 86DAServer Manager 12, 20, 21, 85DAServer Manager book 21DAServer Manager documentation 18, 21DAServer Manager tree 18DAServer version 61Data Highway 26, 29, 30Data Highway Plus 11, 19, 26DCOM 10DDE 11DDEStatus 62Default update interval 33Delete device groups 33Demo mode 14Device group 12, 53Device Group Definitions 32Device Groups 15, 19, 21Device Groups box 32Device Groups dialog box 32Device Groups tab 21, 32Device hierarchy 15, 21device integration clients 86Device Protocol 85DH Node Number 31DH Plus Node Address 24, 25DH Plus Node Number 28, 29, 30, 31DH485 26, 31Diagnostics 10Diagnostics tool 87Dynamic Data Exchange 10dynamically linked 87EEdit mode 18Edit update intervals 33element 37, 45FFastDDE 10Features 10, 13file # 37, 45Firmware Path 24, 25GGetting Started Quickly 17Group 53Group name 12HHelp menu 21Hierarchical location 53Hierarchy 22HMI 10Hot-configuration functionalities 36IIndex 89IOStatus 62Item name 12, 13Item Names 37LLicense Manager 14Link name 12Log Flag data 64MM1785KA Object 26M1785KA object 19M1785KA5 Object 26ABDHPLUS DAServer User’s Guide

90 IndexM1785KA5 object 19M1785KEBR Object 26M1785KEBR object 19Make edits on device groups 33Manual or automatic service 19, 22Maximum Queued Messages 24, 26Message Packet Size 28, 29Microsoft Management Console 20, 85middleware component 87MMC 20, 85ModBus 87NNetDDE 11Network transport protocol 10New_M1785KA_000 Parameters 29New_M1785KA5_000 Parameters 31New_M1785KABR_000 Parameters 30New_M1785KEBR_000 Parameters 29New_PKT_CARD_000 Parameters 23New_PLC5_DHP_000 Parameters 27New_SLC500_DHP_000 Parameters 28New_SSTPCI_CARD_000 Parameters 25Node name 12, 13OOPC 10PPCI Adapters 11PCI Card 24, 26Peer-to-peer unsolicited messaging 35PKT_CARD object 18, 23PLC and Bridge-Module objects 26PLC disconnect 62PLC Protocol Layer 85PLC5_DHP Object 26PLC5_DHP object 19Plu-g-in Component 85Poke command 63Poke Mode settings 21Processor Type 24, 25ProgID 12Program name 12RSlow poll mode 62SMC 20, 85Snap-in environment 18, 21SSTPCI_CARD object 18, 23stand-alone configuration utility 87Stand-alone DAServers 87Status file information 39SuiteLink 10System Management Console 15, 18, 20TTerminating Resistor Enabled 25To prepare the ABDHPLUS DAServer 17Topic name 13Transition mode 21UUnsolicited messages 34Update Interval 34Update Interval column 33Use different configuration sets 35VValue Time Quality (VTQ) 10WWindowViewer 62WinSock 10Wonderware folder 18Wonderware InTouch 9XX45XML-enabled program 87Receive unsolicited messages 35reference 85Remote Reference formulas 64Reply Timeout 28, 29Reply time-out 62Rockwell Software RSLinx 9SSCADA 10Scan Based Message Handling 33Service 19, 22Setup.exe 17, 20SLC500_DHP Object 26SLC500_DHP object 19ABDHPLUS DAServer User’s Guide