BASEstar[TM] Classic DAS for Allen-Bradley Data_Highway[TM]_Protocol___________________________ Installation and User's Guide Order Number: AA-R210A-TE November 1996 This manual describes how to install and use the DAS for Allen-Bradley Data Highway Protocol for BASEstar Classic on OpenVMS. Revision/Update Information: This is a revised document. Operating System and Version: OpenVMS/Alpha Version 6.1 Operating System and Version: OpenVMS/VAX Version 5.5-2 Interface Software and Version:ASEstar Classic Version 3.4 Software Version: BASEstar Classic DAS for Allen-Bradley Data Highway Protocol, Version 3.4 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ November 1996 Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1990, 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha, BASEstar, Digital, OpenVMS, TK, VAX, and the Digital logo. PLC, PLC-2, and PLC-3 are registered trademarks of Allen- Bradley Company Inc. PLC-5, Data Highway and Data Highway Plus are trademarks of Allen-Bradley Company, Inc. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CDROM. This document was prepared using DEC DOCUMENT Version 3.0. _________________________________________________________________ Contents Preface................................................... vi 1 Overview of DAS for AB Data Highway Protocol 1.1 Description................................... 1-1 1.2 Device Communications......................... 1-1 1.3 Supported Functions and Devices............... 1-3 2 Installing the DAS for AB Data Highway Protocol 2.1 Installation Requirements..................... 2-1 2.1.1 Hardware Requirements..................... 2-1 2.1.2 Software Requirements..................... 2-2 2.1.3 Optional Software......................... 2-2 2.1.4 Disk Space Requirements................... 2-3 2.2 Installing DAS for AB Data Highway Protocol... 2-3 2.2.1 Files Created During Installation......... 2-6 2.2.2 Installation Messages..................... 2-6 2.3 Postinstallation Tasks........................ 2-8 2.3.1 Editing the Configuration File............ 2-8 2.3.1.1 Editing Type Records.................... 2-8 2.3.1.2 Editing Path Records.................... 2-13 2.3.1.3 Editing Device Records.................. 2-15 2.3.1.4 DAS for AB Data Highway Protocol Configuration File...................... 2-17 2.3.2 Creating 6001 Net Messages................ 2-21 2.3.3 DAS SPT Block Usage....................... 2-22 2.3.4 Configuring Ports......................... 2-22 2.3.5 Setting Up Plant-Floor Equipment.......... 2-24 2.4 Tracing Device Communications................. 2-24 2.5 Failures During Product Use................... 2-25 iii 3 Using the DAS for AB Data Highway Protocol 3.1 Accessing the DAS for AB Data Highway Protocol Functions..................................... 3-1 3.2 Structured Data............................... 3-2 3.3 Supported Functions........................... 3-2 3.3.1 Start and Stop............................ 3-3 3.3.1.1 PLC-1774................................ 3-4 3.3.1.2 PLC-3................................... 3-5 3.3.1.3 PLC-5................................... 3-5 3.3.2 Upload and Download....................... 3-5 3.3.2.1 PLC-1774................................ 3-6 3.3.2.2 PLC-2................................... 3-8 3.3.2.3 PLC-3................................... 3-11 3.3.2.4 PLC-5................................... 3-11 3.3.3 Read and Write Data....................... 3-13 3.3.3.1 PLC-1774................................ 3-15 3.3.3.2 PLC-2................................... 3-15 3.3.3.3 PLC-3................................... 3-16 3.3.3.4 PLC-5................................... 3-18 3.3.4 Read Status............................... 3-30 3.4 Automatic Data Collection..................... 3-32 3.4.1 Unsolicited Data Collection............... 3-32 3.4.2 Pollsets.................................. 3-34 Index Examples 3-1 Read Data................................. 3-13 3-2 READ DATA With Structured Data............ 3-14 3-3 WRITE DATA................................ 3-14 3-4 WRITE DATA with Structured Data........... 3-14 3-5 Read Status Screen........................ 3-32 iv Figures 1-1 DAS for AB Data Highway Protocol Communications............................ 1-3 Tables 1-1 Allen-Bradley Devices and Supported Functions................................. 1-4 2-1 Disk Space Requirements................... 2-3 2-2 Allen-Bradley and BASEstar Classic Device Connection Management Files............... 2-6 2-3 CREATE TYPE............................... 2-10 2-4 CREATE PATH............................... 2-14 2-5 Line Parameters........................... 2-15 2-6 CREATE DEVICE............................. 2-16 3-1 Allen-Bradley Devices and Functions....... 3-3 3-2 Start and Stop Function................... 3-4 3-3 Download Function......................... 3-7 3-4 Upload Function........................... 3-8 3-5 Download Function......................... 3-13 3-6 Read and Write Data Functions............. 3-18 3-7 Data Format General Reference............. 3-19 3-8 Input File Addresses...................... 3-20 3-9 Output File Addresses..................... 3-21 3-10 Status File Addresses..................... 3-21 3-11 Binary File Addresses..................... 3-21 3-12 Timer File Addresses...................... 3-22 3-13 Counter File Addresses.................... 3-23 3-14 Control File Addresses.................... 3-23 3-15 Integer File Addresses.................... 3-24 3-16 Floating Point File Addresses............. 3-25 3-17 ASCII File Addresses...................... 3-25 3-18 Long Integer File Addresses............... 3-25 3-19 PID Control File Addresses................ 3-26 3-20 Internal Storage File Addresses........... 3-28 3-21 Shared Data File Addresses................ 3-28 3-22 Block Transfer Data Addresses............. 3-28 3-23 String Data Addresses..................... 3-29 v 3-24 Adapter Status File Addresses............. 3-29 3-25 Message Addresses......................... 3-29 vi _________________________________________________________________ Preface This document describes how to install and use BASEstar Classic DAS for Allen-Bradley Data Highway Protocol. Intended Audience This document is intended for system managers who must set up and maintain the following: o BASEstar Classic for OpenVMS software o BASEstar Classic DAS for Allen-Bradley Data Highway Protocol This document is also intended for application programmers who develop plant-floor management software layered on the BASEstar Classic software. Readers of this document should have a solid understanding of OpenVMS operations and administration, as well as OpenVMS application software. In addition, knowledge of the Allen-Bradley PLCs and the specific requirements of the installation site is essential. Document Structure This document is organized as follows: o Chapter 1 provides an overview of the DAS for AB Data Highway Protocol. o Chapter 2 provides information you need to install the DAS for AB Data Highway Protocol. o Chapter 3 provides information about the supported functions for Allen-Bradley PLCs, and how to access the functions. vi Associated Documents Further information on topics covered in this document can be found in the following documents: o BASEstar Classic Installation Guide o BASEstar Classic Configuration and Tuning Guide o BASEstar Classic Menu Interface User's Guide o BASEstar Classic Command Line Interface User's Guide o BASEstar Classic Introduction to Callable Services o BASEstar Classic Guide to Writing Device Access Software o BASEstar Classic Application Programming Interface Reference Guide Information on Allen-Bradley addressing and programming can be found in the following documents. o Allen-Bradley Data Highway/Data Highway Plus Protocol and Command Set o Allen-Bradley 6001 Net Network Communication Software User's Manual o Pyramid Integrator System Addressing Reference o PLC-5 Family Addressing Reference o PLC-3 Family Addressing Reference o PLC-2 Family Addressing Reference o PLC-5/250 Programming Software o PLC-5 Programming Software Conventions This document uses the following conventions: Boldface Highlights user input within textual descriptions. Press the key labeled Return. Unless otherwise specified, press after entering a command or responding to a prompt. vii Enter Type the words or symbols described and press . viii 1 _________________________________________________________________ Overview of DAS for AB Data Highway Protocol This chapter provides an overview of the BASEstar Classic DAS for Allen-Bradley Data Highway Protocol. It also briefly describes Allen-Bradley PLCs and the supported functions for the DAS for AB Data Highway Protocol. 1.1 Description The BASEstar Classic DAS for Allen-Bradley Data Highway Protocol allows you to access Allen-Bradley PLCs through BASEstar Classic device connection management. Device connection management is the device connection/control component of BASEstar Classic for OpenVMS. BASEstar Classic software is designed to facilitate the integration of manufacturing equipment and applications, accelerate the development of integrated manufacturing systems, and provide an architecture for consistent development of manufacturing applications. Using the DAS for AB Data Highway Protocol, users or applications can perform a variety of device access functions, including: reading and writing data, uploading and downloading logic programs, and reading the status of a device. 1.2 Device Communications The DAS for AB Data Highway Protocol consists of two protocol emulators (PEs) and two network interfaces (NIs). The PE and NI work together to provide device-specific communications for BASEstar Classic device connection management's generic callable services. The PE translates BASEstar Classic device connection management's generic services into a device-understandable format. The PE also converts device-specific protocol into a BASEstar Classic device connection management format. Overview of DAS for AB Data Highway Protocol 1-1 Overview of DAS for AB Data Highway Protocol 1.2 Device Communications The NI works directly with a OpenVMS driver or the Allen- Bradley 6001 Net communications software to send data to and receive data from plant-floor devices. 1-2 Overview of DAS for AB Data Highway Protocol Overview of DAS for AB Data Highway Protocol 1.2 Device Communications The DAS for AB Data Highway Protocol has two possible configurations. You can configure the AB Protocol Emulator (PE) to work with the AB6001 Network Interface (NI) and Allen-Bradley's 6001 Net driver, or with the DH1 NI and the Digital terminal driver. The NI communicates the requests and data translated by the PE. Figure 1-1 shows how the DAS for AB Data Highway Protocol facilitates communications between device connection management and the devices. NOTE: Allen-Bradley's 6001 Net is not available on OpenVMS /Alpha systems. Figure 1-1 DAS for AB Data Highway Protocol Communications The embedded responses feature is supported by the AB6001 NI but not the DH1 NI. Embedded responses is a switch selectable option in the Data Highway Communications Adapter (1771-KE, 1771-KF, 1771-KF2) and must be disabled if the DH1 NI is being used. 1.3 Supported Functions and Devices You can perform only the BASEstar Classic device connection management functions that are supported by a device's PE. These functions can be accessed through BASEstar Classic library management and BASEstar Classic device connection management's menu system, commands, and callable services. The DAS for AB Data Highway Protocol supports the following BASEstar Classic device connection management functions: o Start and stop operations on a device o Upload the contents of a device's memory to an OpenVMS file o Download an OpenVMS file to a device's memory o Read data from a specific address in a device's memory o Write data to a specific address in a device's memory Overview of DAS for AB Data Highway Protocol 1-3 Overview of DAS for AB Data Highway Protocol 1.3 Supported Functions and Devices o Read status for a device The DAS for AB Data Highway Protocol supports a variety of devices, as shown in Table 1-1. Table_1-1_Allen-Bradley_Devices_and_Supported_Functions__________ Read Write Read Device____Upload__DownloadStart___Stop____Data____Data____Status_ PLC-1774 X X X X X X X PLC-2 X X X X X family PLC-3 X X X X X X X family PLC-5/10 X X X X X X X PLC-5/11 X X X X X X X PLC-5/12 X X X X X X X PLC-5/15 X X X X X X X PLC-5/20 X X X X X X X PLC-5/25 X X X X X X X PLC-5/30 X X X X X X X PLC-5/40 X X X X X X X PLC-5/60 X X X X X X X PLC-5/80 X X X X X X X PLC-5 X X X X X /250_____________________________________________________________ For more information about the supported functions, refer to Chapter 3 of this document. 1-4 Overview of DAS for AB Data Highway Protocol 2 _________________________________________________________________ Installing the DAS for AB Data Highway Protocol This chapter provides the information you need to install the DAS for AB Data Highway Protocol and to configure your system. 2.1 Installation Requirements Review the following hardware and software requirements to ensure that your system is prepared for the DAS for AB Data Highway Protocol installation. ________________________ Note ________________________ Back up the disks on your system before installing this software. This will provide a method to restore your system in the event of an installation problem. The procedure for backing up disks is described in the OpenVMS System Management Utilities Reference Manual. ______________________________________________________ 2.1.1 Hardware Requirements The following minimum hardware is required for the installation and operation of DAS for AB Data Highway Protocol components. o Any OpenVMS system configuration that has an RS-232 serial port or LAT port connection and is valid for BASEstar Classic Clasic for OpenVMS. o Any of the following Allen-Bradley PLCs: o Allen-Bradley PLC-1774 o Allen-Bradley PLC-2 family of devices o Allen-Bradley PLC-3 family of devices Installing the DAS for AB Data Highway Protocol 2-1 Installing the DAS for AB Data Highway Protocol 2.1 Installation Requirements o Allen-Bradley PLC-5/10, PLC-5/11, PLC-5/12, PLC-5/15, PLC-5/20, PLC-5/25, PLC-5/30, PLC-5/40, PLC-5/60, PLC-5/80, PLC-5/250 o ANSI compatible video display terminal 2.1.2 Software Requirements The following Digital software must be installed prior to installing the DAS for AB Data Highway Protocol: o OpenVMS Version 5.5-2 or higher (VAX) o OpenVMS Version 6.1 or higher (Alpha) o VAX/FMS Version 2.3 or Version 2.4 (required only when the menu system will be used) (The Menu System is available only on OpenVMS/VAX systems.) o BASEstar Classic for OpenVMS, Release 3.4 For information on installing the above software, refer to the BASEstar Classic Installation Guide. ________________________ Note ________________________ Before using this product on a system, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). For more information about the License Management Utility, refer to the License Management Utility Manual for OpenVMS. ______________________________________________________ 2.1.3 Optional Software o Allen-Bradley's 6001 Net Communications Software, Version B/02 or Version 2.4, compatible with OpenVMS Version 5.5-2 or higher (VAX) NOTE: Allen-Bradley's 6001 Net is not available on OpenVMS /Alpha systems. 2-2 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.1 Installation Requirements 2.1.4 Disk Space Requirements Table 2-1 lists the disk space required to install the DAS for AB Data Highway Protocol. The space requirements are approximations; actual sizes may vary depending on your system environment, configuration, and software options selected. Table_2-1_Disk_Space_Requirements__________________________ Approximate Space Requirements Peak/Net_Usage____________(Blocks)_________________________ Peak usage (during 550 (VAX) installation) 750 (Alpha) Net usage (after 400 (VAX) installation) _______________________________510_(Alpha)_________________ 2.2 Installing DAS for AB Data Highway Protocol When your system meets all hardware and software requirements, you can install the DAS for AB Data Highway Protocol. The installation takes from 1 to 5 minutes, depending on system load and configuration. Install the DAS for AB Data Highway Protocol by using the following steps: 1. Log in to a privileged system manager's account. 2. Set the default directory to SYS$UPDATE: $ SET DEFAULT SYS$UPDATE 3. Invoke VMSINSTAL: $ @SYS$UPDATE:VMSINSTAL DCM_ABVV034 ddcu: Installing the DAS for AB Data Highway Protocol 2-3 Installing the DAS for AB Data Highway Protocol 2.2 Installing DAS for AB Data Highway Protocol The DCM_ABVV034 argument is the kit name. The 034 portion of the name is the version number. The ddcu argument represents the name of the device on which the installation media is mounted, where: o dd is the device code o c is the controller designation o u is the unit number VMSINSTAL prompts you for information during the installation. Note that DECnet software does not need to be running to perform the installation procedure. The following is an example of the output from the installation: OpenVMS VAX Software Product Installation Procedure V6.1 It is 11-OCT-1996 at 09:55. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: DCM_ABVV V3.4 Beginning installation of DCM_ABVV V3.4 at 09:56 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright (C) Digital Equipment Corporation 1989, 1996. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, usr, or copying of this software and media is authorized only pusuant to a valid written license from Digital or an authorized sublicensor. BASEstar Classic DAS for Allen-Bradley Data Highway Protocol installation procedure. 2-4 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.2 Installing DAS for AB Data Highway Protocol Checking for a valid license... Product: DAS-AB-CL Producer: DEC Version: 3.4 Release Date: 01-SEP-1996 * Does this product have an authorization key registered and loaded? y Now checking OpenVMS version... Now checking that BASEstar Classic is installed... Now checking disk space... * Do you wish to delete obsolete files [YES]? * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? The installation procedure has no further questions to ask and will complete in 1 to 5 minutes depending on the system and system load. The configuration template file for AB support, DCM_AB_CONFIG.TEMPLATE, is used to define the Allen Bradley paths, types, and devices. Edit this file, as necessary, to reflect your specific site configuration. During installation it will be placed in the directory BCC$SYSDATA. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Copyright (C) Digital Equipment Corporation 1989, 1996. All rights reserved. Executing the Installation Verification Procedure. BASEstar Classic DAS for Allen-Bradley Data Highway Protocol installation procedure has succeeded. Installation of DCM_ABVV V3.4 completed at 09:59 VMSINSTAL procedure done at 09:59 Installing the DAS for AB Data Highway Protocol 2-5 Installing the DAS for AB Data Highway Protocol 2.2 Installing DAS for AB Data Highway Protocol 2.2.1 Files Created During Installation Table 2-2 lists the files that the DAS for AB Data Highway Protocol installation procedure creates and the directories in which they are placed. Table 2-2 Allen-Bradley and BASEstar Classic Device __________Connection_Management_Files______________________ Directory_____________Filename_____________________________ BCC$SYSDATA: DCM_AB_CONFIG.TEMPLATE AB_MSG.DAT SYS$LIBRARY: ILAN_AB.EXE ILAN_AB5.EXE ILAN_DH1.EXE ILAN_AB6001.EXE (VAX) ILAN_AB_SCMP.EXE (VAX) SYS$HELP DCM_ABVV034.RELEASE_NOTES (VAX) ______________________DCM_ABVA034.RELEASE_NOTES_(Alpha)____ 2.2.2 Installation Messages You may see VMSINSTAL messages during the installation procedure. The following messages are specific to the DAS for AB Data Highway Protocol installation: BADBCC, BASEstar Classic software must be installed before DAS for AB Data Highway Protocol. Explanation: Error. Incorrect version of or missing BASEstar Classic software. User Action: Install BASEstar Classic for OpenVMS, Release 3.4 or higher software. BADDCM, BASEstar Classic Device Connect must be installed before the DAS for AB Data Highway Protocol. Explanation: Error. Incorrect version of or missing BASEstar Classic DCM software. User Action: Install BASEstar Classic DCM for OpenVMS, Release 3.4 or higher software. 2-6 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.2 Installing DAS for AB Data Highway Protocol BADVMS (VAX), The DAS for AB Data Highway Protocol must be installed under OpenVMS V5.5-2 or greater. Explanation: Error. Incorrect version of OpenVMS. User Action: Install OpenVMS V5.5-2 or higher. BADVMS (Alpha), The DAS for AB Data Highway Protocol must be installed under OpenVMS V6.1 or greater. Explanation: Error. Incorrect version of OpenVMS. User Action: Install OpenVMS V6.1 or higher. NETBLOCKS (VAX), DAS for AB Data Highway Protocol requires 400 blocks after installation. Explanation: Error. Not enough disk space to complete installation. User Action: Delete any unnecessary files, then reinstall. NETBLOCKS (Alpha), DAS for AB Data Highway Protocol requires 510 blocks after installation. Explanation: Error. Not enough disk space to complete installation. User Action: Delete any unnecessary files, then reinstall. NOLICENSE, No license found for this product - IVP will not be run., Explanation: Informational. A valid license was not found. The installation will continue, but the IVP will not be run. User Action: Register and load a valid license for this product before attempting to use the DAS. NOLOAD, License for this product not loaded - IVP will not be run., Explanation: Informational. The license for this product has not been loaded by the License Management Utility. The installation willl proceed, but the IVP will not be run. User Action: Load the license using the License Management Utility before attempting to use the DAS. Installing the DAS for AB Data Highway Protocol 2-7 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks 2.3 Postinstallation Tasks This section describes the tasks to perform after installing the DAS for AB Data Highway Protocol including editing the configuration file, setting the device connection management support block parameter, configuring ports, and setting up plant-floor equipment. 2.3.1 Editing the Configuration File A configuration file, BCC$SYSDATA:DCM_AB_CONFIG.TEMPLATE, is supplied with the DAS kit. The configuration file contains definitions for types, paths, and devices. A type record represents a protocol emulator (PE). A path record represents a network interface (NI). You must edit this configuration file to include site-specific information about types and paths before you execute this file. The following sections contain examples of type, path, and device records. Refer to the BASEstar Classic Command Line Interface User's Guide for more information about creating type, path, and device definitions. 2.3.1.1 Editing Type Records The following example shows the type records created by the configuration file: create type AB_PLC_1774/manufacturer=AB/model="PLC-1774"/protocol=AB - /description="Allen Bradley Bulletin 1774 Programmable Controller"/log create type AB_PLC_2/manufacturer=AB/model="PLC-2"/protocol=AB - /description="Allen Bradley PLC-2 Programmable Controller"/log create type AB_PLC_205/manufacturer=AB/model="PLC-2/05"/protocol=AB - /description="Allen Bradley PLC-2/05 Programmable Controller"/log create type AB_PLC_215/manufacturer=AB/model="PLC-2/15"/protocol=AB - /description="Allen Bradley PLC-2/15 Programmable Controller"/log create type AB_PLC_216/manufacturer=AB/model="PLC-2/16"/protocol=AB - /description="Allen Bradley PLC-2/16 Programmable Controller"/log create type AB_PLC_217/manufacturer=AB/model="PLC-2/17"/protocol=AB - /description="Allen Bradley PLC-2/17 Programmable Controller"/log create type AB_PLC_220/manufacturer=AB/model="PLC-2/20"/protocol=AB - /description="Allen Bradley PLC-2/20 Programmable Controller"/log 2-8 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks create type AB_PLC_230/manufacturer=AB/model="PLC-2/30"/protocol=AB - /description="Allen Bradley PLC-2/30 Programmable Controller"/log create type AB_PLC_3/manufacturer=AB/model="PLC-3"/protocol=AB - /description="Allen Bradley PLC-3 Programmable Controller"/log create type AB_PLC5_10/manufacturer=AB/model="PLC-5/10"/protocol=AB5 - /description="Allen Bradley PLC-5/10 Programmable Controller"/log create type AB_PLC5_11/manufacturer=AB/model="PLC-5/11"/protocol=AB5 - /description="Allen Bradley PLC-5/11 Programmable Controller"/log create type AB_PLC5_12/manufacturer=AB/model="PLC-5/12"/protocol=AB5 - /description="Allen Bradley PLC-5/12 Programmable Controller"/log create type AB_PLC5_15/manufacturer=AB/model="PLC-5/15"/protocol=AB5 - /description="Allen Bradley PLC-5/15 Programmable Controller"/log create type AB_PLC5_20/manufacturer=AB/model="PLC-5/20"/protocol=AB5 - /description="Allen Bradley PLC-5/20 Programmable Controller"/log create type AB_PLC5_25/manufacturer=AB/model="PLC-5/25"/protocol=AB5 - /description="Allen Bradley PLC-5/25 Programmable Controller"/log create type AB_PLC5_30/manufacturer=AB/model="PLC-5/30"/protocol=AB5 - /description="Allen Bradley PLC-5/30 Programmable Controller"/log create type AB_PLC5_40/manufacturer=AB/model="PLC-5/40"/protocol=AB5 - /description="Allen Bradley PLC-5/40 Programmable Controller"/log create type AB_PLC5_60/manufacturer=AB/model="PLC-5/60"/protocol=AB5 - /description="Allen Bradley PLC-5/60 Programmable Controller"/log create type AB_PLC5_80/manufacturer=AB/model="PLC-5/80"/protocol=AB5 - /description="Allen Bradley PLC-5/80 Programmable Controller"/log create type AB_PLC5_250/manufacturer=AB/model="PLC-5/250"/protocol=AB5 - /description="Allen Bradley PLC-5/250 Programmable Controller"/log create type AB_PLC_IM/manufacturer=AB/model="PLC-IM"/protocol=AB5 - /description="Allen Bradley Interface Module"/log Table 2-3 lists the types and parameters of the CREATE TYPE command, and indicates the parameters of the previous example that you can change. Installing the DAS for AB Data Highway Protocol 2-9 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks Table_2-3_CREATE_TYPE______________________________________ Type________Parameter___Modifiable?________________________ AB_PLC_ Manufacturer No 1774 Model No Protocol No Description Yes AB_PLC_2 Manufacturer No Model No Protocol No Description Yes AB_PLC_205 Manufacturer No Model No Protocol No Description Yes AB_PLC_215 Manufacturer No Model No Protocol No Description Yes AB_PLC_216 Manufacturer No Model No Protocol No Description Yes AB_PLC_217 Manufacturer No Model No Protocol No Description Yes AB_PLC_220 Manufacturer No Model No Protocol No Description Yes AB_PLC_230 Manufacturer No (continued on next page) 2-10 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks Table_2-3_(Cont.)_CREATE_TYPE______________________________ Type________Parameter___Modifiable?________________________ Model No Protocol No Description Yes AB_PLC_3 Manufacturer No Model No Protocol No Description Yes AB_PLC5_10 Manufacturer No Model No Protocol No Description Yes AB_PLC5_11 Manufacturer No Model No Protocol No Description Yes AB_PLC5_12 Manufacturer No Model No Protocol No Description Yes AB_PLC5_15 Manufacturer No Model No Protocol No Description Yes AB_PLC5_20 Manufacturer No Model No Protocol No (continued on next page) Installing the DAS for AB Data Highway Protocol 2-11 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks Table_2-3_(Cont.)_CREATE_TYPE______________________________ Type________Parameter___Modifiable?________________________ Description Yes AB_PLC5_25 Manufacturer No Model No Protocol No Description Yes AB_PLC5_30 Manufacturer No Model No Protocol No Description Yes AB_PLC5_40 Manufacturer No Model No Protocol No Description Yes AB_PLC5_60 Manufacturer No Model No Protocol No Description Yes AB_PLC5_80 Manufacturer No Model No Protocol No Description Yes AB_PLC5_ Manufacturer No 250 Model No Protocol No Description Yes AB_IM[1] Manufacturer No Model No [1]Any_interface_module_is_acceptable,_including_the_1785-_ KA. (continued on next page) 2-12 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks Table_2-3_(Cont.)_CREATE_TYPE______________________________ Type________Parameter___Modifiable?________________________ Protocol No ____________Description____Yes_____________________________ 2.3.1.2 Editing Path Records The following example shows the path records created by the configuration file: create path AB_PATH_5 /vaxport="KTA995:"/netname=AB6001- /io_size=1600/multidrop/log create path AB6001_PATH_6/vaxport="KTA996:"/netname=AB6001- /io_size=1600/multidrop/log create path DH1_PATH_5/vaxport="LTA995:"/netname=DH1- /io_size=1600/multidrop/log/line=(speed=9600) create path DH1_PATH_7 /vaxport="LTA997:"/netname=DH1- /io_size=1600/multidrop/log/line=(speed=9600) Note that you must modify the netname of any device that currently uses the AB6001 Net NI and has a netname of AB. The netname must be changed from AB to AB6001. Allen-Bradley's 6001 Net paths are created only on VAX systems. Table 2-4 lists the paths and parameters of the CREATE PATH command, and indicates the parameters of the previous example that you can change. Verify that the VAXport and the line parameters match your plant-floor configuration. Installing the DAS for AB Data Highway Protocol 2-13 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks Table_2-4_CREATE_PATH______________________________________ Path_____________Parameter___Modifiable?___________________ AB_PATH_5[1] VAXport Yes Netname Yes Multidrop No I/O size Yes Retries Yes Line Yes AB6001_PATH_ VAXport Yes 6[1] Netname Yes Multidrop No I/O size Yes Line Yes DH1_PATH_5 VAXport Yes Netname Yes Multidrop No I/O size Yes Retries Yes Line Yes DH1_PATH_7 VAXport Yes Netname Yes Multidrop No I/O size Yes Line Yes [1]Allen-Bradley's_6001_Net_paths_are_created_on_VAX_______ systems only. ___________________________________________________________ Devices using DH1_PATH_5 and DH1_PATH_7 require the DH1 NI and LTA995 and LTA997 ports. Devices using AB_PATH_ 5 and AB6001_PATH_6 and ports KTA995 and KTA996 require the Allen-Bradley 6001 Net Communication software. For information on configuring the 6001 NET network configuration software, refer to the Allen-Bradley 6001 2-14 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks NET Network Communication Software User's Manual. Allen- Bradley's 6001 NET software is available on VAX systems only. Table_2-5_Line_Parameters__________________________________ Parameter___Modifiable?_Value(s)___________________________ Stop Bits No 1 Data Bits No 8 Parity Yes Even, None Speed Yes 300-19200 Full No Full Duplex Echo No NoEcho Host Synch Yes TT Synch Yes Typeahead No Typeahead Hangup No Hangup Modem Yes Dialup Yes Disconnect_____Yes_________________________________________ 2.3.1.3 Editing Device Records The following example shows the device records created by the configuration file: create dev AB_1771_KE /path=AB_PATH_5 /type=AB_PLC_IM /netaddr="22"/log create dev AB_215 /path=AB_PATH_5/type=AB_PLC_215 /timeout=120- /netaddr="15"/log create dev AB_1785_KA /path=AB6001_PATH_6 /type=AB_PLC_IM /netaddr="2"/log create dev AB_5_15 /path=AB6001_PATH_6 /type=AB_PLC5_15 /timeout=120- /netaddr="1"/log create dev AB_1770_KF2/path=DH1_PATH_7 /type=AB_PLC_IM /netaddr="3"/log create dev AB_5_250 /path=DH1_PATH_7 /type=AB_PLC5_250 /timeout=120- /netaddr="1"/log Installing the DAS for AB Data Highway Protocol 2-15 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks Table 2-6 lists the devices and parameters of the CREATE DEVICE command, and indicates the parameters of the previous example that you can change. Table_2-6_CREATE_DEVICE____________________________________ Device______Parameter___Modifiable?________________________ AB_1771_ Path Yes KE[1] Type No Timeout Yes Netaddr Yes AB_215[1] Path Yes Type No Timeout Yes Netaddr Yes AB_1785_ Path Yes KA[1] Type No Timeout Yes Netaddr Yes AB_5_15[1] Path Yes Type No Timeout Yes Netaddr Yes AB_1770_ Path Yes KF2 Type No Timeout Yes Netaddr Yes AB_5_250 Path Yes Type No Timeout Yes Netaddr Yes [1]Allen-Bradley's_6001_Net_devices_are_created_on_VAX_____ systems only. ___________________________________________________________ 2-16 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks 2.3.1.4 DAS for AB Data Highway Protocol Configuration File The following is an example of the DAS for AB Data Highway Protocol configuration file: $! $! Allen Bradley support for DCM Device Access. $! $! $!********************************************************************! $! ! $! This is a template for the Allen-Bradley site specific ! $! configuration command file. Rename and edit this command ! $! procedure template to reflect your site specific Allen-Bradley ! $! configuration. You must manually execute this command ! $! procedure to configure your devices. ! $! ! $! Add comments to the site specific changes here. ! $! ! $!********************************************************************! $! $ bstar !*********************************************************************! ! The AB5 DAS PE sets the maximum unsolicited id to 127. ! ! The maximum unsolicited id is used by the PE to calculate the ! ! size of the PE listen table. If more or less than 127 ! ! unsolicited id's are required then override the default by ! ! defining the BASEstar Classic parameter ILAN$AB5_MAX_UNSOL_ID ! | and setting it to the desired number. ! !*********************************************************************! ! create parameter ILAN$AB5_MAX_UNSOL_ID/- ! format=value/default=127/min=1/max=2147483647/log ! set parameter ILAN$AB5_MAX_UNSOL_ID 150 Installing the DAS for AB Data Highway Protocol 2-17 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks !*********************************************************************! ! By default the AB5 DAS PE queues 5 reads for unsolicited ! ! requests. During a burst of unsolicited messages there may ! ! be periods where all five unsolicited read requests are ! ! being processed. If a new message arrives while all five ! ! read requests are being processed then an error message is ! ! logged and the message is discarded. If messages are being ! ! lost then the number of read requests can be increased by ! ! defining the BASEstar Classic parameter ILAN$AB5_UNSOL_QUEUE_SIZE! ! and setting it to a larger value then the default value. ! !*********************************************************************! ! create parameter ILAN$AB5_UNSOL_QUEUE_SIZE/- ! format=value/default=5/min=1/max=100 ! set parameter ILAN$AB5_UNSOL_QUEUE_SIZE 10 !*********************************************************************! ! By default, the AB6001 NI assumes that Version 2.4 of ! ! Allen-Bradley 6001 NET software is installed. If version B/02 ! ! is installed, the BASEstar Classic parameter ILAN$AB6001_VERSION! ! must be set to the string "B/02" so that the NI can properly ! ! communicate with 6001 NET. If the parameter is set to a value ! ! that is unknown to the NI or the parameter is not created, the ! ! default version of V2.4 is used. This parameter is only ! ! necessary if the AB6001 NI is used. ! !*********************************************************************! ! create parameter ILAN$AB6001_VERSION/- ! format=string/default="V2.4" ! set parameter ILAN$AB6001_VERSION "V2.4" exit $! $ bstar dcm !*********************************************************************! ! ! ! Create types for the models supported by the AB PE. In ! ! general, the type definitions are DAS specific, and should ! ! not be modified. ! ! ! !*********************************************************************! create type AB_PLC_1774/manufacturer=AB/model="PLC-1774"/protocol=AB - /description="Allen Bradley Bulletin 1774 Programmable Controller"/log 2-18 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks create type AB_PLC_2/manufacturer=AB/model="PLC-2"/protocol=AB - /description="Allen Bradley PLC-2 Programmable Controller"/log create type AB_PLC_205/manufacturer=AB/model="PLC-2/05"/protocol=AB - /description="Allen Bradley PLC-2/05 Programmable Controller"/log create type AB_PLC_215/manufacturer=AB/model="PLC-2/15"/protocol=AB - /description="Allen Bradley PLC-2/15 Programmable Controller"/log create type AB_PLC_216/manufacturer=AB/model="PLC-2/16"/protocol=AB - /description="Allen Bradley PLC-2/16 Programmable Controller"/log create type AB_PLC_217/manufacturer=AB/model="PLC-2/17"/protocol=AB - /description="Allen Bradley PLC-2/17 Programmable Controller"/log create type AB_PLC_220/manufacturer=AB/model="PLC-2/20"/protocol=AB - /description="Allen Bradley PLC-2/20 Programmable Controller"/log create type AB_PLC_230/manufacturer=AB/model="PLC-2/30"/protocol=AB - /description="Allen Bradley PLC-2/30 Programmable Controller"/log create type AB_PLC_3/manufacturer=AB/model="PLC-3"/protocol=AB - /description="Allen Bradley PLC-3 Programmable Controller"/log !*********************************************************************! ! ! ! Create types for the models supported by the AB5 PE. In ! ! general, the type definitions are DAS specific, and should ! ! not be modified. ! ! ! !*********************************************************************! create type AB_PLC5_10/manufacturer=AB/model="PLC-5/10"/protocol=AB5 - /description="Allen Bradley PLC-5/10 Programmable Controller"/log create type AB_PLC5_11/manufacturer=AB/model="PLC-5/11"/protocol=AB5 - /description="Allen Bradley PLC-5/11 Programmable Controller"/log create type AB_PLC5_12/manufacturer=AB/model="PLC-5/12"/protocol=AB5 - /description="Allen Bradley PLC-5/12 Programmable Controller"/log create type AB_PLC5_15/manufacturer=AB/model="PLC-5/15"/protocol=AB5 - /description="Allen Bradley PLC-5/15 Programmable Controller"/log create type AB_PLC5_20/manufacturer=AB/model="PLC-5/20"/protocol=AB5 - /description="Allen Bradley PLC-5/20 Programmable Controller"/log create type AB_PLC5_25/manufacturer=AB/model="PLC-5/25"/protocol=AB5 - /description="Allen Bradley PLC-5/25 Programmable Controller"/log Installing the DAS for AB Data Highway Protocol 2-19 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks create type AB_PLC5_30/manufacturer=AB/model="PLC-5/30"/protocol=AB5 - /description="Allen Bradley PLC-5/30 Programmable Controller"/log create type AB_PLC5_40/manufacturer=AB/model="PLC-5/40"/protocol=AB5 - /description="Allen Bradley PLC-5/40 Programmable Controller"/log create type AB_PLC5_60/manufacturer=AB/model="PLC-5/60"/protocol=AB5 - /description="Allen Bradley PLC-5/60 Programmable Controller"/log create type AB_PLC5_80/manufacturer=AB/model="PLC-5/80"/protocol=AB5 - /description="Allen Bradley PLC-5/80 Programmable Controller"/log create type AB_PLC5_250/manufacturer=AB/model="PLC-5/250"/protocol=AB5 - /description="Allen Bradley PLC-5/250 Programmable Controller"/log create type AB_PLC_IM/manufacturer=AB/model="PLC-IM"/protocol=AB5 - /description="Allen Bradley Interface Module"/log !*********************************************************************! ! ! ! Modify these path and device definitions for your specific ! ! configuration. ! ! ! !*********************************************************************! !*********************************************************************! ! ! ! Create a 6001-NET LAT path using KT devices and the AB6001 NI. ! ! ! !*********************************************************************! ! create path AB_PATH_5 /vaxport="KTA995:"/netname=AB6001- ! /io_size=1600/multidrop/log ! create path AB6001_PATH_6/vaxport="KTA996:"/netname=AB6001- ! /io_size=1600/multidrop/log !*********************************************************************! ! ! ! Create DH1 LAT paths using LT devices and the DH1 NI. ! ! ! !*********************************************************************! ! create path DH1_PATH_5/vaxport="LTA995:"/netname=DH1- ! /io_size=1600/multidrop/log/line=(speed=9600) ! create path DH1_PATH_7 /vaxport="LTA997:"/netname=DH1- ! /io_size=1600/multidrop/log/line=(speed=9600) 2-20 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks !*********************************************************************! ! ! ! Create a 1771-KE and a PLC-215 using the AB6001 NI. ! ! ! !*********************************************************************! ! create dev AB_1771_KE /path=AB_PATH_5 /type=AB_PLC_IM /netaddr="22"/log ! ! create dev AB_215 /path=AB_PATH_5/type=AB_PLC_215 /timeout=120- ! /netaddr="15"/log ! create dev AB_1785_KA /path=AB6001_PATH_6 /type=AB_PLC_IM /netaddr="2"/log ! create dev AB_5_15 /path=AB6001_PATH_6 /type=AB_PLC5_15 /timeout=120- ! /netaddr="1"/log !*********************************************************************! ! ! ! Create a 1770-KF2 and PLC-5/250 using the DH1 NI ! ! ! !*********************************************************************! ! create dev AB_1770_KF2/path=DH1_PATH_7 /type=AB_PLC_IM /netaddr="3"/log ! create dev AB_5_250 /path=DH1_PATH_7 /type=AB_PLC5_250 /timeout=120- ! /netaddr="1"/log $ exit For more information about maintaining type, path, and device definitions, refer to the BASEstar Classic Command Line Interface User's Guide. 2.3.2 Creating 6001 Net Messages If you use the AB6001 NI, you must create a file for Allen- Bradley 6001 Net messages. The message file supplements the system messages with 6001 Net messages. 6001 Net is only available on VAX systems. The following DCL procedure creates the message file. The message file must be set for each BASEstar Classic device connection management user by using the DCL SET MESSAGE command when they log onto the VAX. Installing the DAS for AB Data Highway Protocol 2-21 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks $! Create nonexecutable 6001 Net message file $! $! extract the message object file from the 6001 Net library $ library/extract=6001msg/output=6001msg sys$netv:6001netv.olb $! $! link the message file as a nonexecutable message file $ link/shareable=sys$message:6001msg 6001msg.obj $! $! supplement the system message file with the 6001 Net message file $ set message sys$message:6001msg $ exit 2.3.3 DAS SPT Block Usage The ILAN$MAX_SPT_REQUESTS parameter specifies the maximum number of blocks allocated in the SPT (support) global section. To set this parameter, perform the following steps: 1. Approximate the SPT blocks for the DAS for AB Data Highway Protocol by using the following formula: SPT = 1 + num_paths + (6 * num_devices) The num_paths argument is the number of paths defined in the configuration file. The num_devices argument is the number of devices defined in the configuration file. The SPT argument is the number of blocks for the DAS for AB Data Highway Protocol used in calculating the total block requirements. 2. Use the SPT to calculate the total block requirements for the ILAN$MAX_SPT_REQUESTS parameter. Refer to the BASEstar Classic Configuration and Tuning Guide for instructions on calculating the total block requirements. 2.3.4 Configuring Ports A device can be physically connected to a local area transport (LAT) port. To use a LAT port with the DAS, you must define the LAT port on the VAX system by using the LAT control program. The following DCL example shows how to define port_2 on the LAT node srvr4 as LTA992. It is very important when defining the LAT port to use the /NOQUEUE option. If the port is owned by another process 2-22 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks device connection management reports an error during the establishment of a connection to the device. When you define a path and a device to BASEstar Classic device connection management LTA992 is supplied as the VAXport. $ MCR LATCP LCP> CREATE PORT LTA992 LCP> SET PORT LTA992 /NODE=srvr4/PORT=port_2/NOQUEUE For the DAS for AB Data Highway Protocol to send and receive data correctly you must set and define LAT port characteristics to match the line parameters of the path definition for devices and terminals connected to the LAT. An example of the characteristics set at the LAT prompt follows: Local> DEF PORT n SPEED 9600 Local> DEF PORT n AUTOBAUD DISABLED Local> DEF PORT n AUTOCONNECT DISABLED Local> DEF PORT n FLOW DISABLED Local> DEF PORT n PREFERRED NONE Local> DEF PORT n ACCESS REMOTE Local> DEF PORT n CHAR 8 Local> DEF PORT n PARITY NONE You must also set the following SYSGEN parameters to access Allen-Bradley PLCs to reduce the potential for data overruns. Use the SYSGEN utility to display the current values and AUTOGEN to reset the values accordingly. For information on using SYSGEN and AUTOGEN, refer to the OpenVMS System Management Manual for details. ___________________________________________________________ Parameter________Value_____________________________________ TTY_ALTALARM 0 TTY_ALTYPAHD_____1024______________________________________ To enable use of the alternate typeahead buffer, type the following command from DCL: $ SET TERM LTA992:/ALTYPEAHD/PERMANENT Installing the DAS for AB Data Highway Protocol 2-23 Installing the DAS for AB Data Highway Protocol 2.3 Postinstallation Tasks 2.3.5 Setting Up Plant-Floor Equipment To set up your plant-floor equipment, refer to the Allen- Bradley documentation for your specific device. 2.4 Tracing Device Communications The DAS for AB Data Highway Protocol has built into it the capability to trace PLC communications and to send this output to either a file or a user terminal. The purpose of this tracing is to allow the troubleshooting of PLC communications. To enable tracing do the following: o Set the following logical to 1: DCM_AB$DH1_TRACE Trace the NI (Network Interface) The logical name must be defined in a scope that will be seen by the device server process (ILAN$DEVSRV). o Set the trace output logical to a file or other output device: DCM_AB$DH1_TRACE_ Trace the NI (Network Interface) OUTPUT The logical name must be defined in a scope that will be seen by the device server process (ILAN$DEVSRV). o Start the tracing. To start tracing for the NI, disable all devices on the line for which tracing is desired and reenable them. The trace logical is read when the first device on the line is enabled. The trace output is flushed to the file after every 100 lines that are traced, so trace output may lag actual device I/O. To turn tracing off, reverse the steps used to turn tracing on. 2-24 Installing the DAS for AB Data Highway Protocol Installing the DAS for AB Data Highway Protocol 2.5 Failures During Product Use 2.5 Failures During Product Use If an error occurs while this product is in use and you believe the error is caused by a problem with the product, take one of the following actions: o If you have a Software Product Services Support Agreement, contact your Customer Support Center (CSC) by telephone or by using the electronic means provided with your support agreement (such as DSNlink). The CSC provides telephone support for high-level advisory and remedial assistance. When you initially contact the CSC, indicate the following: - The name and version number of the operating system you are using - The version number of the product you are using - The version number of BASEstar Classic you are using - The hardware system you are using (such as a model number) - The Allen-Bradley PLCs you are communicating with - A brief description of the problem (one sentence if possible) - How critical the problem is o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you do not have any type of software services support agreement and you purchased this product within the past year, you can submit an SPR if you think the problem is caused by a software error. When you submit an SPR, take the following steps: 1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. Include the description and version number of the product being used. Demonstrate the problem with specific examples. 2. Reduce the problem to as small a size as possible. 3. Remember to include listings of any command files, INCLUDE files, or relevant data files, and so forth. Installing the DAS for AB Data Highway Protocol 2-25 Installing the DAS for AB Data Highway Protocol 2.5 Failures During Product Use 4. Report only one problem per SPR. This will facilitate a faster response. 5. Mail the SPR package to Digital. 2-26 Installing the DAS for AB Data Highway Protocol 3 _________________________________________________________________ Using the DAS for AB Data Highway Protocol This chapter provides information about the supported functions for Allen-Bradley PLCs, and how to access these functions. 3.1 Accessing the DAS for AB Data Highway Protocol Functions DAS for AB Data Highway Protocol functions are accessed through the BASEstar Classic device connection management: o Commands o Menu system o Callable services To use the BASEstar Classic device connection management commands, enter the following command at the DCL prompt ($): $ BSTAR DCM For additional information about the BASEstar Classic device connection management commands, refer to the BASEstar Classic Command Line Interface User's Guide. To use the BASEstar Classic device connection management menu system, enter the following command: $ BSTAR/MENU For additional information about the BASEstar Classic device connection management menu system, refer to the BASEstar Classic Menu Interface User's Guide. ________________________ Note ________________________ The menu system is available on OpenVMS/VAX systems only. ______________________________________________________ Using the DAS for AB Data Highway Protocol 3-1 Using the DAS for AB Data Highway Protocol 3.1 Accessing the DAS for AB Data Highway Protocol Functions For additional information about the BASEstar Classic device connection management callable services, refer to the BASEstar Classic Introduction to Callable Services. 3.2 Structured Data The DAS for AB Data Highway Protocol supports the use of structured data. Structured data is a block of data, typically represented by a buffer, that can be broken down into meaningful elements of data. Structured data allows you to impose a structure on the data formats for any given read or write operation. A structure tells the device how to interpret the data that it is reading or writing. For example, temperature and humidity data could be packed into a longword and a word in a buffer. The buffer is then said to contain structured data, with the longword representing temperature, and the word representing humidity. Structured data can represent synchronized data elements from a single source, such as a plant-floor device. Structured data can also represent composite views of different data elements from different sources, such as the total part counts from several different plant-floor devices. For the DAS for AB Data Highway Protocol, all data types, except bit strings, are supported for structured data. 3.3 Supported Functions The following sections describe the functions that are supported by the DAS for AB Data Highway Protocol. Table 3-1 displays the Allen-Bradley PLCs and the functions these devices support. 3-2 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-1_Allen-Bradley_Devices_and_Functions____________________ Read Write Read Device____Upload__DownloadStart___Stop____Data____Data____Status_ PLC-1774 X X X X X X X PLC-2 X X X X X family PLC-3 X X X X X X X family PLC-5/10 X X X X X X X PLC-5/11 X X X X X X X PLC-5/12 X X X X X X X PLC-5/15 X X X X X X X PLC-5/20 X X X X X X X PLC-5/25 X X X X X X X PLC-5/30 X X X X X X X PLC-5/40 X X X X X X X PLC-5/60 X X X X X X X PLC-5/80 X X X X X X X PLC-5 X X X X X /250_____________________________________________________________ 3.3.1 Start and Stop The start and stop functions change the operating mode of a device. The start function enables outputs and the stop function disables outputs. These functions are not supported for the PLC-2 family of devices. _______________________ Warning _______________________ Devices can control complex and perhaps dangerous industrial processes. Do not use the start and stop functions until you take the required safety precautions and required operating restrictions are put into effect. Refer to the manufacturer's documentation for specific safety precautions. ______________________________________________________ Using the DAS for AB Data Highway Protocol 3-3 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions 3.3.1.1 PLC-1774 The start function enables outputs and scanning on the PLC-1774 device. Using the STOP command when the keyswitch position is RUN/PROGRAM LOAD - RUN causes the status of the device to appear as Remote Test. A subsequent START command enables outputs. Table 3-2 displays the keyswitch positions, current mode, request types, DAS activity, and resulting mode for the PLC-1774 while performing the start and stop functions. Table_3-2_Start_and_Stop_Function________________________________ Keyswitch Current DAS Position_________Mode________FunctionActivity____Resulting_Mode__ PROGRAM LOAD Program Start Invalid Program load load mode Program Stop None Program load load TEST MONITOR Test mode Start Invalid Test mode Test mode Stop None Test RUN MONITOR Run mode Start Enable Run outputs Run mode Stop Disable Run outputs RUN/PROGRAM Remote run Start Enable Remote run LOAD - RUN scan- ning,Enable outputs Remote run Stop Disable Remote test outputs RUN/PROGRAM Remote Start Enable Remote test LOAD - TEST test scanning Remote Stop None Remote test test (continued on next page) 3-4 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-2_(Cont.)_Start_and_Stop_Function________________________ Keyswitch Current DAS Position_________Mode________FunctionActivity____Resulting_Mode__ RUN/PROGRAM Remote Start Invalid Remote prog LOAD - PROG prog mode Remote Stop None Remote prog _________________prog____________________________________________ ________________________ Note ________________________ PLC-1774 outputs are disabled with a STOP command, but scanning is not stopped. ______________________________________________________ 3.3.1.2 PLC-3 The start function changes the current mode to Run. The stop function changes the current mode to Program Load. 3.3.1.3 PLC-5 The Start function changes the device operating mode to Remote Run. The Stop function changes the device operating mode to Remote Program. The device keyswitch must be in the REM position for the start or stop request to change the device's operating mode. 3.3.2 Upload and Download The upload function transfers the contents of a device's memory to an OpenVMS file. You can specify the STOP qualifier when using the UPLOAD command. If you specify the STOP qualifier, the PE prevents the contents of PLC memory from being modified during the upload. All BASEstar Classic device connection management write functions are rejected with a device busy message. The download function transfers the contents of an OpenVMS file to a device's memory. You can specify the STOP and RESTART qualifiers to control the device mode when using the DOWNLOAD command. The PE does not allow the operating status of a PLC to be changed unless specified in the DOWNLOAD command. Using the DAS for AB Data Highway Protocol 3-5 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions You must specify the STOP qualifier when you download a running device. The STOP qualifier is a safety mechanism. You must specify the RESTART qualifier to start the device when the download is completed. All device connection management read (except read status) and write functions are rejected with a device busy message during the download. 3.3.2.1 PLC-1774 When you perform the upload function, the keyswitch must be in the RUN-MONITOR, RUN/PROGRAM LOAD, or TEST-MONITOR position. If the keyswitch is in the RUN/PROGRAM LOAD position, the PLC programming terminal must have the device mode set to Remote RUN-MONITOR or TEST-MONITOR. The STOP qualifier for a PLC-1774 upload function prevents other processes from writing to the device through the DAS. The syntax for the STOP qualifier follows: UPLOAD dev_name filename /QUALIFIER="STOP" When you perform the download function, the keyswitch must be in the RUN-MONITOR, RUN/PROGRAM LOAD, or TEST-MONITOR position. If the keyswitch is in the RUN/PROGRAM LOAD position, the PLC programming terminal must have the device mode set to Remote RUN-MONITOR or Remote TEST-MONITOR. There are two qualifiers associated with the download operation: o STOP The STOP qualifier for a PLC-1774 allows the device to be downloaded while running. The PLC-1774 cannot be downloaded without the STOP qualifier because it must be scanning when the download is initiated. 3-6 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions o RESTART The RESTART qualifier sends both scan enable and enable outputs commands to the device when the download completes. The syntax for the STOP and RESTART qualifiers follows: DOWNLOAD dev_name filename /QUALIFIER="STOP/RESTART" ________________________ Note ________________________ You cannot download a PLC-1774 without stopping the device. STOP is a mandatory qualifier. ______________________________________________________ Table 3-3 displays the modes, qualifiers, and supported functions when you use the download function: Table_3-3_Download_Function______________________________________ After Download Keyswitch Position_________QualifiersScan__________Outputs___Mode__________ RUN MONITOR Stop Disable Disable RUN outputs outputs Stop Enable Enable RUN /Restart outputs outputs RUN/PROGRAM Stop Disable Disable Remote test LOAD - RUN outputs outputs Stop Enable Enable Remote run /Restart outputs outputs TEST MONITOR Stop Disable Not TEST outputs modified Stop Enable Not TEST /Restart outputs modified RUN/PROGRAM Stop Disable Not Remote test LOAD - TEST outputs modified (continued on next page) Using the DAS for AB Data Highway Protocol 3-7 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-3_(Cont.)_Download_Function______________________________ After Download Keyswitch Position_________QualifiersScan__________Outputs___Mode__________ Stop Enable Not Remote test, _________________/Restart__outputs_______modified__remote_run____ 3.3.2.2 PLC-2 You can perform the upload function for the PLC-2 devices in any mode. If you issue the UPLOAD command with the STOP qualifier, the device is issued an upload request. If you are using a 1771-KA interface card and issue the UPLOAD command with the STOP qualifier, the device is issued a download request. The STOP qualifier disables the industrial terminal as well as preventing other processes from writing to the device through the DAS. Table 3-4 displays the interface, modes, qualifiers, and functions supported, modified, and not supported by the upload function. Table_3-4_Upload_Function__________________________________ Interface_Mode______QualifieRead________Write______________ 1771-KA Prog None Not Not supported supported Remote None Not Not supported prog supported Prog Stop Not Not supported supported Remote Stop Not Not supported prog supported Run None Supported Supported Remote None Supported Supported run Test None Supported Supported (continued on next page) 3-8 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-4_(Cont.)_Upload_Function__________________________ Interface_Mode______QualifieRead________Write______________ Run test None Supported Supported Run Stop Supported Not supported Remote Stop Supported Not supported run Test Stop Supported Not supported Run test Stop Supported Not supported 1771-KA2 Prog None Not Not supported supported Remote None Not Not supported prog supported Prog Stop Not Not supported supported Remote Stop Not Not supported prog supported Run None Supported Supported Remote None Supported Supported run Test None Supported Supported Run test None Supported Supported Run Stop Supported Not supported Remote Stop Supported Not supported run Test Stop Supported Not supported __________Run_test__Stop____Supported___Not_supported______ ________________________ Note ________________________ Uploading with the STOP qualifier disables the industrial terminal until the upload function is completed. ______________________________________________________ Using the DAS for AB Data Highway Protocol 3-9 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions The action taken for the download function (and associated qualifiers) for a PLC-2 family device depends on the communications interface card being used with the device. Certain revisions of the 1771-KA2 communications adapter do not allow a logic program to be downloaded to the memory of a PLC-2/20 in the RUN/PROG mode. To determine whether or not the combination of a given revision of the 1771-KA2 interface and PLC-2/20 processor produces this problem, contact an Allen-Bradley representative. Until Allen-Bradley releases a revision of hardware that allows downloading in the RUN/PROG mode, some PLC-2/20s may only be downloaded in the PROG mode. The 1771-KA interface does not support the SET DATA TABLE SIZE command. The file data table downloaded must have the same data table size as the destination device. If the download function fails with an invalid data table size error, check the history file for the file data table size and reset the device data table size using an industrial terminal. Using the download function through a 1771-KA2 interface sets the device data table size to match the download file data table size. Valid download functions for the 1771-KA1 and 1771-KA2 interfaces are: o TEST or RUN/PROG Test mode - perform download function with the STOP and RESTART qualifiers o PROG or RUN/PROG Prog mode - perform download function with no qualifier or the STOP qualifier o RUN or RUN/PROG Run mode - perform download function with the STOP and RESTART qualifiers ________________________ Note ________________________ The RUN and RUN/PROG Run mode are not supported through the 1771-KA interface during the download function. The RUN and TEST modes are not supported through the 1771-KA2 interface during the download function. The read and write functions are not supported during a download function on a PLC-2 device. ______________________________________________________ 3-10 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions You must specify the STOP qualifier if the device is to be stopped by the download function. Use the RESTART qualifier to restart the device after the download function is completed. 3.3.2.3 PLC-3 You can perform the upload function for the PLC-3 devices in any mode. The STOP qualifier prevents other processes from writing to the device through the DAS. PLC-3 file allocations are frozen during the upload function regardless of the STOP qualifier. The controller performs the upload function until the end of the program is reached. Following the upload function, the PLC-3 is returned to its original state. You can perform the download function for a PLC-3 family device in any mode. If the device is in Run or Test mode, the STOP qualifier is mandatory. If you specify the RESTART qualifier, the device is put in Run mode when the download function completes. If you omit the RESTART qualifier, the device is put in Program mode when the download function completes. The PLC-3's station address is preserved and the station address in the logic file is ignored. To perform the download function, set the keyswitch to the MEMORY PROTECT OFF position. 3.3.2.4 PLC-5 The upload function can be performed by a PLC-5/10, PLC-5 /11, PLC-5/12, PLC-5/15, PLC-5/20, PLC-5/25, PLC-5/30, PLC- 5/40, PLC-5/60 and a PLC-5/80 device in any mode. Upload is not supported for the PLC-5/250. Specifying /QUALIFIER=STOP helps to prevent modification of device memory during an upload. If you specify the STOP qualifier, the device cannot be scanning during the upload function. If the device is in Remote Run or Remote Test and you specify the STOP qualifier, the device mode is changed to Remote Program until the upload function completes. Note that the PLC-5/15 (Series B, Revision E, or earlier) does not support any read functions except read status during an upload function when you specify the STOP qualifier. Using the DAS for AB Data Highway Protocol 3-11 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions The keyswitch must be in the REMOTE position to use the following qualifiers: o STOP - puts the device in REM PROG mode before performing the upload function o RESTART - puts the device in REM RUN mode after performing the upload function You cannot restart in PROG mode or stop in RUN mode while performing an upload function. The STOP qualifier prevents other processes from writing to the device through the DAS for AB Data Highway Protocol during the upload. When you perform the download function for a PLC-5 family device, the device can be in any mode except RUN mode. The keyswitch position must be REM or PROG. Note that if the device is in Remote Run or Remote Test mode, the STOP qualifier is mandatory. The RESTART qualifier is only valid if the keyswitch is in the REM position. If you specify the RESTART qualifier, the device is put in the Remote Run mode when the download function completes. The download function supports the following qualifiers: o STOP - puts the device in REM PROG mode before performing the download function o RESTART - puts the device in REM RUN mode after performing the download function o OVERRIDE - allows a file from one PLC-5 model to be downloaded to a different PLC-5 model. Without this qualifier, a file may only be downloaded to the same model it was uploaded from. You must specify the STOP qualifier if the device is to be stopped by the download function. Table 3-5 displays the combinations of modes and qualifiers available while performing a download operation. An "N" indicates an invalid combination and a "Y" indicates a valid combination. 3-12 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-5_Download_Function________________________________ ______________________________Qualifiers___________________ Mode________None___Stop___Restart___Stop/Restart___________ RUN N N N N PROG Y Y N N REM RUN N Y N Y REM PROG Y Y Y Y REM_TEST____N______Y______N_________Y______________________ 3.3.3 Read and Write Data Use the read data and write data functions to read data from and write data to a specific address in device storage. Address syntax is specific to each device or device family, and is similar to the syntax used with the Allen-Bradley T3, T4, or T50 programming terminals. The data type formats supported depend on the device. Example 3-1 shows an example of the information displayed when you enter the READ DATA command. Example 3-1 Read Data DCM> read data ab_5/format=array[16]:bit/address="N7:00/00" Device: AB_5 Data starting at address N7:00/00 for ARRAY[16]:BIT element. Data: 0: 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Example 3-2 shows an example of the information displayed when you enter the READ DATA command with structured data. Using the DAS for AB Data Highway Protocol 3-13 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Example 3-2 READ DATA With Structured Data DCM> read data ab_3/addr=I300/form="struct(word,word,word) Device : AB_3 Address : I300 Format : STRUCTURE(S_WORD,S_WORD,S_WORD) Data: 0 : 1 1 : 2 2 : 3 Example 3-3 WRITE DATA DCM> write data ab_5/format=word/address=N7:00 Data Value 1 : 3 Example 3-4 WRITE DATA with Structured Data DCM> WRITE DATA AB_3/addr=I300/form="struct(word,word,word) Device : AB_3 Address : I300 Format : STRUCTURE(S_WORD,S_WORD,S_WORD) Data value 0 : 0 Data value 1 : 0 Data value 2 : 0 Example 3-3 shows an example of the information displayed when you enter the WRITE DATA command. Example 3-4 shows an example of the information displayed when you enter the WRITE DATA command with structured data. The following sections describe the use of the read data and write data functions by specific devices, including addressing and data type formats. 3-14 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions 3.3.3.1 PLC-1774 Addressing and data type formats are necessary for performing the read data and write data functions for the PLC-1774 device. Addressing Legal address formats for the PLC-1774 are: www wwww wwwbb where: www = 0-777 octal word address wwww = 0-1777 octal word address www = 0-377 octal word bb = 0-17 octal bit The following examples are legal addresses for the PLC- 1774: 400 (word 400) 1600 (word 1600) 36610 (word 366, bit 10) Data Type Formats Legal data type formats for the PLC-1774 are bit, word, unsigned word, byte, unsigned byte, and packed decimal. Reading data from the device into the format of word, unsigned word, or packed decimal eliminates the status bits that are present in the internal binary coded decimal format of the device. Writing data to the device from the format of word, unsigned word, or packed decimal is limited to 0-999, and the resulting status bits are cleared. 3.3.3.2 PLC-2 Addressing and data type formats are necessary for performing the read data and write data functions for the PLC-2 family of devices. Using the DAS for AB Data Highway Protocol 3-15 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Addressing The address format for the PLC-2 family is: wwwww/bb where: wwwww = 0-17777 octal word address bb = 0-17 octal bit (optional) The maximum allowable word address differs for each member of the PLC-2 family. The following examples are legal addresses for the PLC-2: 20 (word 20) 372/00 (word 372, bit 00) 17777/17 (word 17777, bit 17) Data Type Formats Legal data type formats for the PLC-2 family are bit, word, unsigned word, byte, unsigned byte, and packed decimal. Reading data from the device into the format of word, unsigned word, or packed decimal eliminates the status bits that are present in the internal BCD format of the device. Data to be written to the device from the format of word, unsigned word, or packed decimal is limited to 0-999, and the resulting status bits are cleared. 3.3.3.3 PLC-3 Addressing and data type formats are necessary for performing the read data and write data functions for the PLC-3 family of devices. Addressing There are two types of addressing for PLC-3 devices: extended addressing and data table addressing. Extended addressing has the general format: E.M.S.S.S.S.W/B where: E is the extended address indicator M is the major area number S is the subarea designation W is the word address B is the bit address 3-16 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions There can be as little as two subarea designations and a maximum of four, depending on which major area is being addressed. Data table addressing simplifies the addressing of the data table, and generally has the format: ASF:W/B where: A is the basic structure: W for word (default), F for file S is the section of the data table: O, I, T, C, N, F, D, B, A, H, P, S F is the file number: 0 - 999 (default is the file 0) W is the word number within the file: 0 - 999; 0 - 7777 octal for I/O B is the bit: 0 - 17 octal within word; 0 - 9999 within file You can access data within each data table section at file, word, or bit levels. Bit numbers are octal for addresses having word structures and decimal for addresses having file structures. For example, you can address the same bit as WN2:4/10, FN2:4/8, or FN2:0/72. In the first address (WN2:4/10), W indicates word structure for integer section data stored in file 2, word 4, bit 10 (octal). The last two addresses (FN2:4 /8 and FN:0/72) use file addressing. In these examples, F indicates file structure. To locate the bit with the address FN2:4/8, the processor counts 8 bits in integer file 2 starting with word 4, bit 0. With the address FN2:0/72, the processor counts 72 bits in integer file 2 starting with word 0, bit 0. Certain data table sections may be addressed differently; refer to the Allen-Bradley PLC-3 Programmable Controller Programming Manual for details. The following examples are legal addresses for the PLC-3: Using the DAS for AB Data Highway Protocol 3-17 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions I370 (input section, rack 37, module 0) FN2:738/17 (integers section, file 2, word 738, bit 17) TACC9990 (timers section, accumulator word, structure 9990) E3.1.9.0.0.1010 (ASCII section (9), word 1010) E3.1.4.0.13.2/7 (counters section (4), structure 13, word 2, bit 7) Data Type Formats Table 3-6 shows the supported data type formats for reading from and writing to the various data table sections of the PLC-3. Table_3-6_Read_and_Write_Data_Functions__________________________ _____________________________Data_Type_Formats___________________ PLC-3 Data Unsigned UnsignedFloating Section___Bit____Word____Word____Byte____Byte____Point___Longword Output X X X X X Input X X X X X Timers X X X X X Counters X X X X X Integers X X X X X Floating X X X X Point Decimal X X X X X Binary X X X X X ASCII X X X High X X X X Order Ints Pointers X X X X X X Status____X______X_______X_______X_______X_______________________ 3.3.3.4 PLC-5 Address syntax and supported device connection management data types for read and write operations vary between the PLC-5/250 and the other PLC-5 family devices. 3-18 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions The following sections describe the use of the read data and write data functions by specific devices, including addressing and data type formats. Addressing and data type formats are necessary for performing the read data and write data functions for the PLC-5 family of devices. Data Type Formats Table 3-7 shows which data type formats are supported for reading from and writing to the various file types of the PLC-5 family. Table_3-7_Data_Format_General_Reference____________________ Device File Type__________Bit___Byte__Word__Long__Float_String_________ Output X X Input X X Status X X Binary X X Timer X X X Counter X X Control X X Integer X X Floating X Point ASCII X X Long Integer X X PID Control X X X Internal X X Storage Shared Data X X Block X X Transfer Data String X X Adapter X X X Status Message_______X_____X_____X________________________________ Using the DAS for AB Data Highway Protocol 3-19 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions General Address Formats The general format for specifying addresses for the PLC-5 family devices is: mFSf:nn/bb or mFSf:nn.mne where: o m = module number (module numbers are used for the PLC-5 /250 only) o FS = file specifier (specifies the device file type) o f = decimal file number o nn = decimal element number o rr = octal rack number o bb = bit address (octal if following rr, decimal if following nn) o mne = sub-element or bit mnemonic Specific Address Formats The following tables describe address specifications and data types for specific PLC-5 family file types. Refer to the general address formats listed above for a description of the conventions used to describe address specifications. Input File Addresses Table 3-8 describes address specifications and data types for input file addresses. Input file addresses are identical for all PLC-5 devices and are specified in octal. Table_3-8_Input_File_Addresses_____________________________ Address_______Format________Comment________________________ I :rr Word Input image table word I_:rr/bb______Bit___________Output_image_table_bit_________ Output File Addresses Table 3-9 describes address specifications and data types for output file addresses. Output file addresses 3-20 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions are identical for all PLC-5 devices and are specified in octal. Table_3-9_Output_File_Addresses____________________________ Address_______Format________Comment________________________ O :rr Word Output image table word O_:rr/bb______Bit___________Output_image_table_bit_________ Status File Addresses Table 3-10 describes address specifications and data types for status file addresses. Status file addresses are identical for all PLC-5 devices, except that a module number must be specified for the PLC-5/250. Table_3-10_Status_File_Addresses___________________________ Address_______Format________Comment________________________ mS:nn Word Status file word mS:nn/bb______Bit___________Status_file_bit________________ Binary File Addresses Table 3-11 describes address specifications and data types for binary file addresses. Binary file addresses are identical for all PLC-5 devices, except that a module number must be specified for the PLC-5/250. Table_3-11_Binary_File_Addresses___________________________ Address_______Format________Comment________________________ mBf:nn Word Binary file word mBf:nn/bb_____Bit___________Binary_file_bit________________ Timer File Addresses Table 3-12 describes address specifications and data types for timer file addresses. Timer file addresses are identical for all PLC-5 devices, except that a module number must be specified for the PLC-5/250. Timers can be read as entire structures or addressed at the sub-element level. Using the DAS for AB Data Highway Protocol 3-21 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions For a PLC-5/250, the accumulator and preset values are longwords and the total structure size is 12. For other PLC-5 family devices, the accumulator and preset values are words. Table_3-12_Timer_File_Addresses____________________________ Address_______Format________Comment________________________ mTf:nn Array[3]:long PLC-5/250 timer structure Tf:nn Array[3]:word PLC-5/[12,15,25] timer structure mTf:PRE Long PLC-5/250 timer preset Tf:PRE Word PLC-5/[12,15,25] timer preset mTf:PRE/bb Bit Timer preset bit mTf:ACC Long PLC-5/250 timer accumulator Tf:ACC Word PLC-5/[12,15,25] timer accumulator mTf:ACC/bb Bit Timer accumulator bit mTf:EN[1] Bit Timer enable bit mTf:TT[1] Bit Timer timing bit mTf:DN[1] Bit Timer done bit [1]_Control_bits_should_be_treated_as_read_only_and________ modified only under PLC program control. Modifying these bits from a computer can give unpredictable results. ___________________________________________________________ Counter File Addresses Table 3-13 describes address specifications and data types for counter file addresses. Counter file addresses are identical for all PLC-5 devices except, that a module number must be specified for the PLC-5/250. Counters can be read as entire structures or addressed at the sub-element level. 3-22 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-13_Counter_File_Addresses__________________________ Address_______Format________Comment________________________ mCf:nn Array[3]:word Entire counter structure mCf:PRE Word Counter preset mCf:PRE/bb Bit Counter preset bit mCf:ACC Word Counter accumulator mCf:ACC/bb Bit Counter accumulator bit mCf:CU[1] Bit Counter up enable bit mCf:CD[1] Bit Counter down enable bit mCf:DN[1] Bit Counter done bit mCf:OV[1] Bit Counter overflow bit mCf:UN[1] Bit Counter underflow bit [1]_Control_bits_should_be_treated_as_read_only_and________ modified only under PLC program control. Modifying these bits from a computer can give unpredictable results. ___________________________________________________________ Control File Addresses Table 3-14 describes address specifications and data types for control file addresses. Control file addresses are identical for all PLC-5 devices, except that a module number must be specified for the PLC-5/250. Table_3-14_Control_File_Addresses__________________________ Address_______Format________Comment________________________ mRf:nn Array[3]:word Entire control structure mRf:nn.LEN Word Control expression files length mRf:nn.LEN Bit Length bit /bb mRf:nn.POS Word Control expression file position mRf:nn.POS Bit Position bit /bb (continued on next page) Using the DAS for AB Data Highway Protocol 3-23 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-14_(Cont.)_Control_File_Addresses__________________ Address_______Format________Comment________________________ mRf:nn.EN[1] Bit Enabled bit mRf:nn.EU[1] Bit Enabled unloading bit mRf:nn.DN[1] Bit Done bit mRf:nn.EM[1] Bit Empty bit mRf:nn.ER[1] Bit Error bit mRf:nn.UL[1] Bit Unload bit mRf:nn.IN[1] Bit Inhibit comparisons bit mRf:nn.FD[1] Bit Found bit [1]_Control_bits_should_be_treated_as_read_only_and________ modified only under PLC program control. Modifying these bits from a computer can give unpredictable results. ___________________________________________________________ Integer File Addresses Table 3-15 describes address specifications and data types for integer file addresses. Integer file addresses are identical for all PLC-5 devices, except that a module number must be specified for the PLC-5/250. Table_3-15_Integer_File_Addresses__________________________ Address_______Format________Comment________________________ mNf:nn Word Integer file word mNf:nn/bb_____Bit___________Integer_file_bit_______________ Floating Point File Addresses Table 3-16 describes address specifications and data types for floating point file addresses. Floating point file addresses are identical for all PLC-5 devices, except that a module number must be specified for the PLC-5/250. 3-24 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-16_Floating_Point_File_Addresses___________________ Address_______Format________Comment________________________ mFf:nn________Float_________Float_file_floating_point______ ASCII File Addresses Table 3-17 describes address specifications and data types for ASCII file addresses. ASCII file addresses are supported only for the PLC-5/10, PLC-5/11, PLC-5/12, PLC-5 /15, PLC-5/20, PLC-5/25, PLC-5/30, PLC-5/40, PLC-5/60 and the PLC-5/80. ASCII addresses must be read from and written to with element counts that are multiples of 2. Table_3-17_ASCII_File_Addresses____________________________ Address_______Format________Comment________________________ Af:nn_________Array[2]:byte_2_ASCII_file_characters________ Long Integer File Addresses Table 3-18 describes address specifications and data types for long integer file addresses. Long integer file addresses are supported only for the PLC-5/250. Table_3-18_Long_Integer_File_Addresses_____________________ Address_______Format________Comment________________________ mLf:nn Word Long integer file longword mNf:nn/bb_____Bit___________Long_integer_file_bit__________ PID Control File Addresses Table 3-19 describes address specifications and data types for PID control file addresses. PID control file addresses are supported only for the PLC-5/250. Using the DAS for AB Data Highway Protocol 3-25 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-19_PID_Control_File_Addresses______________________ Address_______Format________Comment________________________ mPDf:nn Array[164]:bytEntire PID control structure mPDf:nn/bb Bit PID control structure bit mPDf:nn.SP Float Setpoint mPDf:nn.KP Float Proportional gain mPDf:nn.KI Float Integral gain mPDf:nn.KD Float Derivative time mPDf:nn.BIAS Float Output bias % mPDf:nn.MAXS Float Setpoint maximum mPDf:nn.MINS Float Setpoint minimum mPDf:nn.DB Float Deadband mPDf:nn.SO Float Set output % mPDf:nn.MAXO Float Output limit high % mPDf:nn.MINO Float Output limit low % mPDf:nn.UPD Float Update time mPDf:nn.PV Float Process variable mPDf:nn.ERR Float Error mPDf:nn.OUT Float Output mPDf:nn.PVH Float PV alarm high mPDf:nn.PVL Float PV alarm low mPDf:nn.DVP Float Deviation alarm + mPDf:nn.DVN Float Deviation alarm - mPDf:nn.PVDB Float PV alarm deadband mPDf:nn.MAXI Float Input range maximum mPDf:nn.MINI Float Input range minimum mPDf:nn.TIE Float Tieback % mPDf:nn.ADDR Float Address of master loop mPDf:nn.DVDB Float Deviation alarm deadband mPDf:nn.DATA Array[14]:floaReserved - interim use (continued on next page) 3-26 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-19_(Cont.)_PID_Control_File_Addresses______________ Address_______Format________Comment________________________ mPDf:nn.EN[1] Bit PID enable bit mPDf:nn.CT[1] Bit Cascaded type bit mPDf:nn.CL[1] Bit Cascaded loop bit mPDf:nn.PVT[1]Bit PV tracking bit mPDf:nn.DO[1] Bit Derivative off bit mPDf:nn.SWM[1]Bit Software A/M mode bit mPDf:nn.CA[1] Bit Control action bit mPDf:nn.MO[1] Bit Mode bit mPDf:nn.PE[1] Bit PID equation bit mPDf:nn.INI[1]Bit PID initialized bit mPDf:nn.SPOR[1Bit SP out of range bit mPDf:nn.OLL[1]Bit Output limit low bit mPDf:nn.OLH[1]Bit Output limit high bit mPDf:nn.EWD[1]Bit Error within deadband bit mPDf:nn.DVNA[1Bit Deviation high alarm bit mPDf:nn.DVPA[1Bit Deviation low alarm bit mPDf:nn.PVLA[1Bit PV low alarm bit mPDf:nn.PVHA[1Bit PV high alarm bit [1]_Control_bits_should_be_treated_as_read_only_and________ modified only under PLC program control. Modifying these bits from a computer can give unpredictable results. ___________________________________________________________ Internal Storage File Addresses Table 3-20 describes address specifications and data types for internal storage file addresses. Internal storage file addresses are supported only for the PLC-5/250 and are specified in octal. Using the DAS for AB Data Highway Protocol 3-27 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-20_Internal_Storage_File_Addresses_________________ Address_______Format________Comment________________________ IS:rr Word Internal storage file word IS:rr/bb______Bit___________Internal_storage_file_bit______ Shared Data File Addresses Table 3-21 describes address specifications and data types for shared data file addresses. Shared data file addresses are supported only for the PLC-5/250. Table_3-21_Shared_Data_File_Addresses______________________ Address_______Format________Comment________________________ mSDf:nn Word Shared data file word mSDf:nn/bb____Bit___________Shared_bit_____________________ Block Transfer Data Addresses Table 3-22 describes address specifications and data types for block transfer data addresses. Block transfer data addresses are supported only for the PLC-5/250. Table_3-22_Block_Transfer_Data_Addresses___________________ Address_______Format________Comment________________________ mBTDf:nn Word Block transfer data file word mBTDf:nn/bb___Bit___________Block_transfer_data_bit________ String Data Addresses Table 3-23 describes address specifications and data types for string data addresses. String data addresses are supported only for the PLC-5/250. 3-28 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-23_String_Data_Addresses___________________________ Address_______Format________Comment________________________ mSTf:nn String Entire string structure mSTf:nn.LEN Word String length mSTf:nn.DATA__Array[82]:byteString_data-up_to_82_bytes_____ Adapter Status File Addresses Table 3-24 describes address specifications and data types for adapter status file addresses. Adapter status file addresses are supported only for the PLC-5/250 and are specified in octal. Table_3-24_Adapter_Status_File_Addresses___________________ Address_______Format________Comment________________________ ASf:rr Array[4]:byte Entire adapter status structure ASf:rr.RC Byte Adapter status retry count ASf:rr.OI[1] Bit Adapter status output inhibit ASf:rr.CF[1] Bit Adapter status fault [1]_Control_bits_should_be_treated_as_read_only_and________ modified only under PLC program control. Modifying these bits from a computer can give unpredictable results. ___________________________________________________________ Message Addresses Table 3-25 describes address specifications and data types for message addresses. Message addresses are supported only for the PLC-5/250. Table_3-25_Message_Addresses_______________________________ Address_______Format________Comment________________________ mMSGf:nn Array[112]:bytEntire message structure mMSGf:nn.ERR Word Message error code (continued on next page) Using the DAS for AB Data Highway Protocol 3-29 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Table_3-25_(Cont.)_Message_Addresses_______________________ Address_______Format________Comment________________________ mMSGf:nn.ERR Bit Message error code bit /bb mMSGf:nn.RLEN Word Message request length mMSGf:nn.RLEN Bit Message request length bit /bb mMSGf:nn.DLEN Word Message done length mMSGf:nn.DLEN Bit Message done length bit /bb mMSGf:nn.EN[1]Bit Message enable bit mMSGf:nn.ST[1]Bit Message start transmission bit mMSGf:nn.AD[1]Bit Message done bit mMSGf:nn.AE[1]Bit Message error bit mMSGf:nn.CO[1]Bit Message continuous bit mMSGf:nn.EW[1]Bit Message enabled waiting mMSGf:nn.DN[1]Bit Message synchronization done mMSGf:nn.ER[1]Bit Message synchronization error [1]_Control_bits_should_be_treated_as_read_only_and________ modified only under PLC program control. Modifying these bits from a computer can give unpredictable results. ___________________________________________________________ 3.3.4 Read Status The read status function issues a diagnostic status request to the PLC, interprets the device response, and returns the interpretation as a character buffer. An error message is displayed if a device definition does not match the device in the device response. If this occurs, you must correct the device definition before the device can be uploaded or downloaded. Example 3-5 shows an example of the values returned in the status buffer when you enter the READ STATUS command. The BASEstar Classic Command Line Interface User's Guide gives detailed information about the READ STATUS command. The information on the screen varies for each type of device. 3-30 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Values for the devices calling the ILAN$READ_DEVICE_STATUS routine using the /QUALIFIER=binary qualifier are returned in the status buffer. Refer to the Allen-Bradley Data Highway/Data Highway Plus Protocol and Command Set for these values. To display the returned values for device status, enter the following at the BASEstar Classic device connection management prompt: DCM> READ STATUS device-name/FULL Using the DAS for AB Data Highway Protocol 3-31 Using the DAS for AB Data Highway Protocol 3.3 Supported Functions Example 3-5 Read Status Screen Status of Device AB_5 at dd-mmm-yyy hh:mm:ss.ss Interface: PLC-5 processor interface Processor: PLC-5 processor interface Series/Revision: B/E Keyswitch: Remote program load Memory Size: 13824 Data Files: 14 Program Files: 4 Processor Number: 1 I/O Address: 0 Memory Protect: Disabled Forcing Status: No forces present 3.4 Automatic Data Collection The following sections discuss unsolicited data collection and pollsets for the Allen-Bradley PLCs. 3.4.1 Unsolicited Data Collection BASEstar Classic device connection management has the ability to receive data values generated by plant devices without issuing a prior request. To use this unsolicited data collection capability, the devices and physical points must be correctly defined using BASEstar Classic software. For information on defining devices and data for unsolicited collection, refer to the BASEstar Classic Command Line Interface User's Guide. Allen-Bradley PLCs are capable of sending unsolicited messages to an OpenVMS host. In order to generate unsolicited data, the ladder logic program for the Allen-Bradley PLCs must use the Allen-Bradley message instruction. The following components of the message instruction support unsolicited data: o Address and size of the data to be sent o Data Highway address of the communications controller to which the OpenVMS host is connected o Destination (of the data to be sent) table address 3-32 Using the DAS for AB Data Highway Protocol Using the DAS for AB Data Highway Protocol 3.4 Automatic Data Collection The DAS for AB Data Highway Protocol uses the destination table address as the unsolicited ID. Because unsolicited ID's are numeric, the family of the destination device must be PLC-2. For further information about the message instruction, see the Allen-Bradley documentation of your specific device. The DAS for AB Data Highway Protocol allows you to define BASEstar Classic device connection management physical points for collecting unsolicited data. When the device sends an unsolicited message to the OpenVMS host, the DAS for AB Data Highway Protocol forwards the message to BASEstar Classic device connection management. The maximum unsolicited message size allowed is 244 bytes. By default, the maximum unsolicited ID designation allowed is 127. You can override this default by setting the BASEstar Classic parameter ILAN$AB_MAX_UNSOL_ID within the range 0 - 65535. Unsolicited messages are received in the DAS for AB Data Highway Protocol by posting an unsolicited read request for the device. When the device sends an unsolicited message to the DAS for AB Data Highway Protocol, the message is read and sent to BASEstar Classic device connection management and any interested applications. It is possible for the device to send another message before the first one has been processed. Only five unsolicited read requests are queued per device. If six messages are read in quick succession before any of the first five have been processed, the sixth message is discarded. The number of queued unsolicited read requests can be redefined by setting ILAN$AB_UNSOL_QUEUE_SIZE. There is no minimum or maximum number of read requests for the queue size. ________________________ Note ________________________ Increasing either of these parameter values increases the amount of SPT blocks used by the PE. These increases do not take effect until the device is MODIFIED/DISABLED and MODIFIED/ENABLED using BASEstar Classic device connection management. ______________________________________________________ For information on setting parameter values, refer to the BASEstar Classic Guide to Writing Device Access Software. Using the DAS for AB Data Highway Protocol 3-33 Using the DAS for AB Data Highway Protocol 3.4 Automatic Data Collection 3.4.2 Pollsets BASEstar Classic device connection management physical points can be grouped together into pollsets to optimize data collection. Pollsets created for the Allen-Bradley PLCs have the following limitations: o Physical points with different data types cannot be part of the same pollset. For example, a physical point of type WORD and a physical point of type BIT cannot be members of the same pollset. Physical points of the same data type with varying element counts can reside in the same pollset. o The size of any pollset cannot exceed 200 contiguous bytes, regardless of the number of physical points in the pollset. Therefore, the first byte of the physical point with the lowest address cannot be more than 200 bytes away from the last byte of the physical point with the highest address. o Members of pollsets created for the PLC-3 must have identical context, section, and file values. o Pollset members for PLC-5's must have identical file numbers. PLC-5/250 pollset members must have identical module numbers. For more information on physical points, refer to the BASEstar Classic Command Line Interface User's Guide. 3-34 Using the DAS for AB Data Highway Protocol _________________________________________________________________ Index A Device access software _______________________________ (cont'd) Accessing DAS functions, 3-1 overview, 1-1 Addressing supported devices, 3-2 PLC-1774, 3-15 supported functions, 3-2 PLC-2, 3-16 using, 3-1 PLC-3, 3-16 Device communications Automatic data collection, tracing, 2-24 3-32 Device records, 2-15 pollsets, 3-34 Devices, 1-1 unsolicited, 3-32 Allen-Bradley, 1-3 communications, 1-1 C______________________________ Disk space requirements, 2-3 Configuration file Download function, 3-5 device records, 2-15 PLC-1774, 3-6 editing, 2-8 PLC-2, 3-8 example, 2-17 PLC-3, 3-11 path records PLC-5, 3-11 line parameters, 2-13 type records, 2-8 F______________________________ Configuring ports, 2-22 Files created during installation, D______________________________ 2-6 Data type formats Functions, 1-3 PLC-1774, 3-15 PLC-2, 3-16 H______________________________ PLC-3, 3-18 Hardware PLC-5, 3-19 required, 2-1 Device access software accessing functions, 3-1 description of, 1-1 installation requirements, 2-1 Index-1 PLC-2 I______________________________ addressing, 3-16 Installation, 2-1 data type formats, 3-16 files created, 2-6 PLC-3 messages, 2-6 addressing, 3-16 postinstallation tasks, 2-8 data type formats, 3-18 procedure, 2-3 PLC-5 requirements, 2-1 data type formats, 3-19 Pollsets, 3-34 K Postinstallation tasks, 2-8 _______________________________ Problem reporting, 2-25 Keyswitch position, 3-4 Product failure, 2-25 PLC-1774 PROGRAM LOAD, 3-4 R______________________________ RUN MONITOR, 3-4, 3-7 Read data function, 3-13 RUN/PROGRAM LOAD - PROG, PLC-1774, 3-15 3-5 PLC-2, 3-15 RUN/PROGRAM LOAD - RUN, PLC-3, 3-16 3-4, 3-7 PLC-5, 3-18 RUN/PROGRAM LOAD - TEST, structured data, 3-2 3-4, 3-7 Read status function, 3-30 TEST MONITOR, 3-4, 3-7 PLC-5 S PROG, 3-13 _______________________________ REM PROG, 3-13 Software REM RUN, 3-13 optional, 2-2 REM TEST, 3-13 required, 2-1 RUN, 3-13 SPT block usage, 2-22 Start function, 3-3 L______________________________ PLC-1774, 3-4 Line parameters, 2-13 PLC-3, 3-5 PLC-5, 3-5 M Stop function, 3-3 _______________________________ PLC-1774, 3-4 Messages PLC-3, 3-5 installation, 2-6 PLC-5, 3-5 6001 Net, 2-21 Structured data, 3-2 _______________________________ T______________________________ Path records, 2-13 Trace Plant-floor equipment using, 2-24 setting up, 2-24 Type records, 2-8 PLC-1774 addressing, 3-15 data type formats, 3-15 Index-2 PLC-5, 3-11 U______________________________ Unsolicited data collection, W______________________________ 3-32 Write data function, 3-13 Upload function, 3-5 PLC-1774, 3-15 PLC-1774, 3-6 PLC-2, 3-15 PLC-2, 3-8 PLC-3, 3-16 PLC-3, 3-11 PLC-5, 3-18 structured data, 3-2 Index-3