Digital Device Access Software for Modicon® with BASEstar[TM] on_OpenVMS__________________________________________ Installation and User's Guide Order Number: AA-Q5FTB-TE August 1996 This manual describes how to install and use the Digital Device Access Software for Modicon programmable controllers with the BASEstar Open for OpenVMS interface. Revision/Update Information: This is a revised document. Operating System and Version: OpenVMS/Alpha Version 6.1 Operating System and Version: OpenVMS/VAX Version 6.1 Interface Software and Version:ASEstar Open Version 3.0 Software Version: Device Access Software for Modicon, Version 3.0 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ August 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 1994, 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha, BASEstar, DEComni, Digital, OpenVMS, TK, VAX, and the Digital logo. Modicon and Modbus are registered trademarks of AEG Schneider Automation. 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 2.3. _________________________________________________________________ Contents Preface................................................... v 1 Overview 1.1 Description................................... 1-1 1.2 Device Communications......................... 1-2 1.3 Supported Functions and Devices............... 1-2 2 Installing and Configuring the DAS for Modicon Programmable Controllers 2.1 Installation Requirements..................... 2-1 2.1.1 Hardware.................................. 2-1 2.1.2 Software.................................. 2-3 2.1.3 Disk Space................................ 2-3 2.2 Installing the DAS for Modicon Programmable Controllers................................... 2-4 2.2.1 Files Created During Installation......... 2-7 2.2.2 Installation Messages..................... 2-7 2.3 Postinstallation Tasks........................ 2-10 2.3.1 Editing the Configuration Files........... 2-10 2.3.1.1 Editing ODS Registrations............... 2-11 2.3.1.2 Editing BASEstar Open Protocol Profile Definitions............................. 2-14 2.3.1.3 Editing VMD Definitions................. 2-15 2.3.1.4 DAS for Modicon Programmable Controllers Configuration Files..................... 2-19 2.3.2 Configuring Ports......................... 2-23 2.3.3 Setting Up Plant-Floor Equipment.......... 2-24 2.3.4 Tracing Device Communications............. 2-24 2.4 Failures During Product Use................... 2-25 iii 3 Using the DAS for Modicon Programmable Controllers 3.1 Accessing Modicon Functions................... 3-1 3.2 Supported Functions........................... 3-1 3.2.1 Connect, Conclude and Abort Functions..... 3-2 3.2.2 Read and Write Variable Functions......... 3-2 3.2.3 Information Report and Abort Indications............................... 3-7 3.3 Addressing Syntax and Supported Data Types.... 3-8 3.3.1 Modicon Micro 84 Addressing Syntax and Supported Data Types...................... 3-9 3.3.2 Modicon 184 and 384 Addressing Syntax and Supported Data Types...................... 3-9 3.3.3 Modicon 484 Addressing Syntax and Supported Data Types...................... 3-10 3.3.4 Modicon 884 Addressing Syntax and Supported Data Types...................... 3-10 3.3.5 Modicon 584 and 984 Addressing Syntax and Supported Data Types...................... 3-11 A Error Messages Index Examples 2-1 ODS Registration.......................... 2-11 2-2 BASEstar Open Protocol Profile Configuration............................. 2-15 2-3 VMD Configuration......................... 2-15 2-4 DAS for Modicon Programmable Controllers ODS Configuration File.................... 2-19 2-5 DAS for Modicon Programmable Controllers BSTR Configuration File................... 2-21 3-1 UNNAMED_VARIABLE CREATE Command........... 3-4 3-2 UNNAMED_VARIABLE DISPLAY_VALUE Output..... 3-6 3-3 UNNAMED_VARIABLE MODIFY_VALUE Output...... 3-6 iv Figures 1-1 DAS Communications........................ 1-2 2-1 Modbus Communications..................... 2-2 2-2 Modbus RS-232 Pinouts..................... 2-2 2-3 Modbus Plus Communications................ 2-3 Tables 2-1 Disk Space Requirements................... 2-4 2-2 Files Created for the DAS for Modicon Programmable Controllers.................. 2-7 2-3 REGISTER Attributes....................... 2-13 2-4 VMD CREATE................................ 2-18 3-1 Connect, Conclude and Abort Interface Access.................................... 3-2 3-2 Read and Write Variable Types............. 3-3 3-3 Read and Write Variable Interface Access.................................... 3-4 3-4 Indication Interface Access............... 3-8 3-5 Modicon Micro 84 Address Format........... 3-9 3-6 Modicon 184 and 384 Address Format........ 3-9 3-7 Modicon 484 Address Format................ 3-10 3-8 Modicon 884 Address Format................ 3-10 3-9 Modicon 584 and 984 Address Format........ 3-11 v _________________________________________________________________ Preface This document describes how to install and use the Digital Device Access Software for Modicon Programmable Controllers. Intended Audience This document is intended for system managers who must set up and maintain the following: o BASEstar Open software o Digital Device Access Software for Modicon Programmable Controllers This document is also intended for application programmers who develop plant-floor management software layered on BASEstar Open software. Readers of this document should have knowledge of: o OpenVMS operations and administration o OpenVMS application software o BASEstar Open software o Site-specific installation requirements In addition, knowledge of the Modicon programmable controllers is required. v Document Structure This document is organized as follows: o Chapter 1 provides an overview of the DAS for Modicon programmable controllers. o Chapter 2 provides the information you need to install and configure the DAS for Modicon programmable controllers. o Chapter 3 provides information about the supported functions for Modicon programmable controllers, and how to access the functions. Associated Documents For information on installing and configuring a BASEstar Open system, refer to the following documents: o BASEstar Open for OpenVMS Release Notes o BASEstar Open for OpenVMS Installation Guide o BASEstar Open for OpenVMS Management Guide For information on installing and configuring a BASEstar Open system, refer to the following documents: o BASEstar Open for OpenVMS Release Notes o BASEstar Open for OpenVMS Installation Guide o BASEstar Open for OpenVMS Management Guide For information on using BASEstar Open software functions, refer to the following documents: o BASEstar Open for OpenVMS Introduction o BASEstar Open for OpenVMS Reference Guide (Model) o BASEstar Open for OpenVMS Command Language Interface o BASEstar Open for OpenVMS Error Messages Guide For more information on developing software to integrate manufacturing applications and equipment, refer to the following documents: o BASEstar Open for OpenVMS Application Programming Interface vi For information on installing and using DEComni functions, refer to the following documents: o DEComni for OpenVMS Installation Guide o DEComni for OpenVMS Application Programmer's Interface o DEComni for OpenVMS Guide to Using Omni Directory Services o DEComni for OpenVMS Guide to Using OmniView For information on Modicon programmable controller communications and addressing, refer to the following documents: o Modicon Protocol Reference Guide o Modicon DEC Host Based Devices Users Guide 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. Enter Type the words or symbols described and press . vii 1 _________________________________________________________________ Overview This chapter provides an overview of the Digital Device Access Software for Modicon Programmable Controllers. It also briefly describes Modicon programmable controller communications, and the supported functions for the DAS for Modicon programmable controllers. 1.1 Description The DAS for Modicon programmable controllers allows you to access Modicon programmable controllers using BASEstar Open Device Services, BASEstar Open Data Services or DEComni Services. Device Services is the device configuration and data collection component of BASEstar Open for OpenVMS, allowing the user to: o Configure device and variable definitions o Read and write variable values o Configure polled data collection Data Services is the data management component of BASEstar Open for OpenVMS that provides device independent access to shop floor data allowing the user to: o Configure data points o Read and write data point values o Generate events based on data changes DEComni Services provides the Applications Programming Interface (API) used by the BASEstar Open Device/Data Services to communicate with shop floor devices. DEComni uses the Manufacturing Messaging Specification (MMS) (ISO- 9506) model to communicate with shop floor devices. DEComni also has the capability to support non-MMS devices such Overview 1-1 Overview 1.1 Description as Modicon programmable controllers through protocol specific Device Access Software, such as the DAS for Modicon programmable controllers. Using the DAS for Modicon programmable controllers, applications can perform a variety of device access functions for the Modicon programmable controllers. 1.2 Device Communications The DAS for Modicon programmable controllers consists of software that provides device-specific communications for users of the DEComni API. BASEstar Open Device /Data Services use the DEComni API to provide device communications to BASEstar Open users. The DAS software communicates the requests and data directly with an OpenVMS device driver to send data to and receive data from plant-floor devices. Figure 1-1 shows how the DAS for Modicon programmable controllers facilitates communications between BASEstar Open Device or Data Services and the device. Figure 1-1 DAS Communications 1.3 Supported Functions and Devices You can perform only device access funtions that are supported by the DAS. The DAS for Modicon programmable controllers supports the following DEComni Services functions for Modicon programmable controllers: o Initiate a connection to a device (omni_connect) o Conclude a connection with a device (omni_conclude) o Abort a connection with a device (omni_abort) 1-2 Overview Overview 1.3 Supported Functions and Devices o Get a value from a device's memory (omni_get_value) o Put a value to a device's memory (omni_put_value) o Receive an information report from a device's memory (omni_get_indications) o Receive an abort from a device (omni_get_indications) The DAS for Modicon programmable controllers supports the following Modicon programmable controllers: o Modicon Micro 84 controllers o Modicon 184 controllers o Modicon 384 controllers o Modicon 484 controllers o Modicon 584 controllers o Modicon 884 controllers o Modicon 984 controllers o Modicon SQ85, Q984 (Modbus-Plus) (VAX) o Modicon SA85 (Modbus-Plus) (Alpha) For more information about the supported functions for these programmable controllers, refer to Chapter 3 of this document. Overview 1-3 2 _________________________________________________________________ Installing and Configuring the DAS for Modicon Programmable Controllers This chapter provides the information you need to install the DAS for Modicon programmable controllers 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 Modicon programmable controllers installation. 2.1.1 Hardware The hardware requirements for the DAS for Modicon programmable controllers are the same as those for the BASEstar Open software. For specific hardware requirements, refer to the BASEstar Open for OpenVMS Installation Guide . Additional hardware required for configuring the DAS for Modicon programmable controllers using Modbus includes: o Any supported Modicon programmable controller. o J478 Modbus modem to connect to the OpenVMS system. o J478 Modbus modem to connect to the programmable controller. o A cable from the OpenVMS system to the Modbus modem. o J374 Modbus communications adapter if using Modicon 184 or 384 programmable controllers. o J474 Modbus communications adapter if using Modicon 484 programmable controllers. and Configuring the DAS for Modicon Programmable Controllers 2-1 Installing and Configuring the DAS for Modicon Programmable Controllers 2.1 Installation Requirements Figure 2-1 shows the required hardware for each model of programmable controller. Figure 2-1 Modbus Communications The cable to the J478 Modbus modem must be terminated with a 25 pin male RS232-C connector with pinouts as shown in Figure 2-2. Figure 2-2 Modbus RS-232 Pinouts Additional hardware required for configuring the DAS for Modicon programmable controllers using Modbus-Plus includes: o Any supported Modicon 984 programmable controller model that ends in the number 5 (for example Modicon 984/385) o Modicon SQ85 Modbus Plus communications card or Q984 programmable controller (VAX) o Modicon SA85 Modbus Plus communications card (Alpha) The SQ85 or Q984 card fits only into a VAX Q-BUS backplane. The SA85 card fits only into an Alpha ISA backplane. Figure 2-3 shows the hardware required to use Modbus Plus. 2-2 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.1 Installation Requirements Figure 2-3 Modbus Plus Communications 2.1.2 Software The following software must be installed prior to installing DAS for Modicon programmable controllers: o OpenVMS/Alpha Version 6.1 o OpenVMS/VAX Version 6.1 o BASEstar Open for OpenVMS Version 3.0 For more information on installing BASEstar Open software, refer to the BASEstar Open for OpenVMS 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 Disk Space Table 2-1 lists the disk space required to install the DAS for Modicon programmable controllers. The space requirements are approximations; actual sizes may vary depending on your system environment and configuration. and Configuring the DAS for Modicon Programmable Controllers 2-3 Installing and Configuring the DAS for Modicon Programmable Controllers 2.1 Installation Requirements Table_2-1_Disk_Space_Requirements__________________________ Approximate Space Requirements Usage_____________________(Blocks)_________________________ Peak (during 950 (Alpha) installation) 3000 (VAX) Net (after installation) 450 (Alpha) __________________________1500_(VAX)_______________________ 2.2 Installing the DAS for Modicon Programmable Controllers When your system meets all hardware and software requirements, you can install the DAS for Modicon programmable controllers. The installation takes from 1 to 5 minutes, depending on your system load and configuration. Install the DAS for Modicon programmable controllers 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 MODVA030 ddcu: where: o MODVA argument is the kit name o VV in the name means this is an OpenVMS/VAX kit o VA in the name means this is an OpenVMS/Alpha kit o 030 portion of the name is the version number o ddcu argument represents the name of the device on which the installation media is mounted, where: - dd is the device code - c is the controller designation - u is the unit number 2-4 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.2 Installing the DAS for Modicon Programmable Controllers 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 AXP Software Product Installation Procedure V6.1 It is 28-NOV-1995 at 14:03. 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: MODVA V3.0 Beginning installation of MODVA T3.0 at 14:03 %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 1994, 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. Digital Device Access Software for Modicon installation procedure. Checking for a valid license... Product: MODDAS-V Producer: DEC Version: 1.0 Release Date: 01-JUN-1994 * Does this product have an authorization key registered and loaded? y Now checking OpenVMS version... and Configuring the DAS for Modicon Programmable Controllers 2-5 Installing and Configuring the DAS for Modicon Programmable Controllers 2.2 Installing the DAS for Modicon Programmable Controllers Now checking that DEComni is installed... Now checking DEComni version... Now checking DEComni logicals... Now checking the DEComni integrator registration utility... * Do you want BASEstar Open support [YES]? Now checking disk space... * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? ---------------------------------NOTE------------------------------------ During installation the file ODS_MOD_CONFIG.TEMPLATE is copied to the ODS:[SCRIPTS] directory. Copy and edit this file to create site specific /PATH and /LINE directory definitions for devices at your installation. ---------------------------------NOTE------------------------------------ During installation the file BSTR_MOD_CONFIG.TEMPLATE is copied to the BSTR$KIT:[ETC] directory. Copy and edit this file to create site specific VMD definitions. Now modifying the ODS schema to add Modicon specific object classes and attributes... Checking ODS Attribute Type Schema definitions ... Checking ODS Object Class Schema definitions ... Querying ODS Schema definitions ... Valid Schema definitions found in the attribute schema database as: OC ALIASED_NAME CN C L S O OU P_ADDR APC OWNER APT AEQ MAPV SY OBJ_ID BER PSAP S SAP TSAP N_ADDR AS_LIST DESCR VMD DOM DEL VN APPSN APROF VERSION NLEVEL MAX_CALL ED MAX_CALLING MAX_SEG CBB_LIST SS_LIST VENDOR MODEL REV INUM DN SHARE CONT_FILE CAP_FILE PN REUSE ARG MON DOM_LIST VAR ATYPE ADDR_T ADDR_V PATH LINE STATION LI NE_NAME PORT ENQ_RETRIES NAK_RETRIES TIMEOUT SPEED PARITY MODEM TRACE KE_STATION KE_TIMEOUT SLAVE_ADDRESS RETRIES SLAVE_ROUTING NODE_ADDRESS 2-6 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.2 Installing the DAS for Modicon Programmable Controllers Valid Schema definitions found in the object class schema database as: TOP ALIAS C L O OU AP AE DSA DEVICE TAE OAE AS VMD DOMAIN PI NVAR UNVAR DH_LINE DH_PATH MODBUS_PATH MODPLUS_SLAVE_PATH MODPLUS_NODE_PATH MODBUS_LINE MODPLUS_LIN E Normal Completion. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Now registering Digital Device Access Software for Modicon with DEComni... Copyright (C) Digital Equipment Corporation 1994, 1996. All rights reserved. Executing the Installation Verification Procedure. Digital Device Access Software for Modicon installation procedure has succeeded. Installation of MODVA T3.0 completed at 13:14 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]MODVA030.VMI_DATA VMSINSTAL procedure done at 14:04 2.2.1 Files Created During Installation Table 2-2 lists the files created by the DAS for Modicon programmable controllers installation procedure, and the directories in which those files are placed. Table 2-2 Files Created for the DAS for Modicon __________Programmable_Controllers_________________________ Directory________Filename__________________________________ ODS:[SCRIPTS] ODS_MOD_CONFIG.TEMPLATE BSTR$KIT:[ETC]___BSTR_MOD_CONFIG.TEMPLATE__________________ 2.2.2 Installation Messages You may see VMSINSTAL messages during the installation procedure. The following messages are specific to the DAS for Modicon programmable controllers installation: and Configuring the DAS for Modicon Programmable Controllers 2-7 Installing and Configuring the DAS for Modicon Programmable Controllers 2.2 Installing the DAS for Modicon Programmable Controllers BADOMNI, The version of DEComni required is DEComni V3.0 or later., Explanation: Error. This version of the DAS is designed to work with DEComni V3.0 or later. User Action: Install DEComni V3.0 or later and then reinstall the DAS. BADVMS (Alpha), Digital Device Access Software for Modicon Programmable Controllers must be installed under OpenVMS V6.1., Explanation: Error. The DAS is being installed on a version of OpenVMS that is less than OpenVMS V6.1. User Action: Upgrade OpenVMS to the required minimum version and then install the DAS. BADVMS (VAX), Digital Device Access Software for Modicon Programmable Controllers must be installed under OpenVMS V6.1., Explanation: Error. The DAS is being installed on a version of OpenVMS that is less than OpenVMS V6.1. User Action: Upgrade OpenVMS to the required minimum version and then install the DAS. NETBLOCKS (VAX), Digital Device Access Software for Modicon Programmable Controllers requires 1500 blocks after installation., Explanation: Error. There isn't enough space on the system disk to install the DAS. User Action: Delete unneeded files and reattempt the installation. NETBLOCKS (ALPHA), Digital Device Access Software for Modicon Programmable Controllers requires 450 blocks after installation., Explanation: Error. There isn't enough space on the system disk to install the DAS. User Action: Delete unneeded files and reattempt the installation. 2-8 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.2 Installing the DAS for Modicon Programmable Controllers NOETC, Unable to find BSTR$KIT:[ETC] directory., Explanation: Error. The directory to place the BASEstar Open configuration template for Modicon devices was not found. User Action: Reinstall BASEstar Open to set up the BSTR$KIT:[ETC] directory. 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. NOOMNI, DEComni must be installed before Digital Device Access Software for Modicon Programmable Controllers., Explanation: Error. The installation procedure could not verify that DEComni was installed on the system. DEComni installation is a prerequisite to the installation of this DAS. User Action: Install DEComni V3.0 and then reinstall the DAS. NOINTREG, Unable to find the integrator registration utility., Explanation: Error. DEComni provides a registration utility for DASes to use to register their presence with DEComni. This registration utility could not be found. User Action: Reinstall DEComni to provide the required registration utility. and Configuring the DAS for Modicon Programmable Controllers 2-9 Installing and Configuring the DAS for Modicon Programmable Controllers 2.2 Installing the DAS for Modicon Programmable Controllers NOODS, Unable to find the directory for DEComni Directory Services., Explanation: Error. The installation procedure creates classes and attributes in the Omni Directory Services database and this database could not be found. User Action: Reinstall DEComni to set up the Omni Directory Services directory. NOSCRIPT, Unable to find ODS:[SCRIPTS] directory., Explanation: Error. The directory to place the ODS configuration template for Modicon devices was not found. User Action: Reinstall DEComni to set up the Omni Directory Services directory. ODSINI, Omni logicals have not been defined, attempting to define logicals., Explanation: Information. The DAS installation requires that certain DEComni logicals be defined and these logical names were not found. The installation procedure attempts to define the logical names by executing SYS$STARTUP:OMNI_ LOGICALS.COM. User Action: None. 2.3 Postinstallation Tasks Before using the DAS for Modicon programmable controllers you must perform the following postinstallation tasks: o Edit the configuration files o Configure ports o Set up plant-floor equipment 2.3.1 Editing the Configuration Files Configuration files, ODS_MOD_CONFIG.TEMPLATE and BSTR_MOD_ CONFIG.TEMPLATE, are supplied with the DAS for Modicon programmable controllers. The ODS configuration file contains Omni Directory Services (ODS) registration commands for Modicon specific classes and attributes. The BASEstar Open configuration file contains definitions for sample Modicon VMDs and protocol profile(s). 2-10 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Copy the template files and edit them to include site- specific directory, VMD and protocol profile definitions. When you complete your edits, execute the files to create the ODS and BASEstar Open Device Services definitions. The following sections provide examples of ODS and BASEstar Open definitions from the configuration files, and indicate which attributes can be modified. For more information about creating VMD and protocol profile definitions, refer to the BASEstar Open for OpenVMS Command Language Interface. For more information about registering ODS definitions, refer to the DEComni for OpenVMS Guide to Using Omni Directory Services. 2.3.1.1 Editing ODS Registrations ODS registrations allow the DAS software to locate a particular device on an Modicon Modbus network. Example 2-1 shows the configuration file commands that create the ODS registrations. Example 2-1 ODS Registration REGISTER DIRECTORY NAME "/LINE=MODBUS_LINE" ATTRIBUTES "OC=MODBUS_LINE /PORT=LTA207:/RETRIES=3/SPEED=9600/PARITY=none/MODEM=0/TIMEOUT=3/TRACE=0" REGISTER DIRECTORY NAME "/LINE=MODPLUS_LINE" ATTRIBUTES "OC=MODPLUS_LINE /PORT=MPA1:/RETRIES=2/TIMEOUT=2/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MOD984_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=20/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MODPLUS984_SLAVE_PATH" ATTRIBUTES "OC=MODPLUS_SLAVE_PATH/LINE_NAME=(/LINE=MODPLUS_LINE) /SLAVE_ROUTING=03.00.00.00.00/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MODPLUS984_NODE_PATH" ATTRIBUTES "OC=MODPLUS_NODE_PATH/LINE_NAME=(/LINE=MODPLUS_LINE) /NODE_ADDRESS=4/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MOD884_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=21/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MOD584_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=22/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MOD484_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=23/TRACE=0" and Configuring the DAS for Modicon Programmable Controllers 2-11 Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks You can modify the command for your site configuration. Table 2-3 lists ODS attributes, the class they belong to and valid values for the attributes. Attribute values are not checked until a connection is initiated with the VMD. Table 2-3 lists the classes and attributes that are supported for Modicon devices. 2-12 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Table_2-3_REGISTER_Attributes______________________________ Class____________Attribute________Value(s)_________________ MODBUS_LINE PORT TT01:, LTA201:, etc.[1] SPEED 110 - 9600 PARITY NONE, EVEN, ODD MODEM TRUE, ON, YES, 1 or FALSE, OFF, NO, 0 TIMEOUT 2-10[2] RETRIES 0-20 TRACE[3] TRUE, ON, YES, 1 or FALSE, OFF, NO, 0 MODBUS_PATH LINE_NAME /LINE=xxx[4] SLAVE_ADDRESS 1-247 TRACE[3] TRUE, ON, YES, 1 or FALSE, OFF, NO, 0 MODPLUS_LINE PORT MPA1:, MPB1:, MPC1:, MPD1:[5] RETRIES 0-20 TIMEOUT 2-10[2] TRACE[3] TRUE, ON, YES, 1 or FALSE, OFF, NO, 0 MODBUS_SLAVE_ LINE_NAME /LINE=xxx[6] PATH SLAVE_ROUTING xx.xx.xx.xx.xx[7] TRACE[3] TRUE, ON, YES, 1 or FALSE, OFF, NO, 0 MODBUS_NODE_ LINE_NAME /LINE=xxx[8] PATH NODE_ADDRESS 1-64[9] TRACE[3] TRUE, ON, YES, 1 or FALSE, OFF, NO, 0 [1]LTAXXX:_is_used_for_LAT_connections._TTXX:_is_used_for__ direct connection. [2]Seconds. [3]Trace is used to allow troubleshooting of the device communications. See Section 2.3.4 for details. [4]Specify a name registered earlier with ODS that specifies the line that the programmable controller with this slave address will be using. [5]Specify the OpenVMS Modbus Plus device name. A maximum of four cards are allowed per system. [6]Specify a name registered earlier with ODS that specifies the Modbus Plus port that the programmable controller with this slave routing will be using. [7]The slave routing can contain up to 5 routing bytes. If using a bridge the nodes can be 1-64 where the address is node.node.node.node.node (if using the maximum number of bridges). If no bridge is used, then the address would look like node.0.0.0.0. All five routing bytes must be specified even if they are zero. If using a bridge multiplexor, then the last three bytes of the routing information looks like node.port.address where node is the address of the bridge multiplexor (1-64), port is the port on the multiplexor (1-4) and address is the Modbus address (1-247) of the programmable controller. [8]Specify a name registered earlier with ODS that specifies the Modbus Plus port that is associated with this VMS Modbus Plus device. [9]Specify the Modbus Plus node address for the OpenVMS node. Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks ___________________________________________________________ 2.3.1.2 Editing BASEstar Open Protocol Profile Definitions The BASEstar Open protocol profile is used to associate a device with the correct DAS. Example 2-2 shows the configuration file commands that create protocol profile definitions. 2-14 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Example 2-2 BASEstar Open Protocol Profile Configuration CREATE PROTOCOL_PROFILE mod_m84 -APPLPROFID 101 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_184 -APPLPROFID 102 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_384 -APPLPROFID 103 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_484 -APPLPROFID 104 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_584 -APPLPROFID 105 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_884 -APPLPROFID 106 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_984 -APPLPROFID 107 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE modplus_984 -APPLPROFID 108 -MAXPDUSIZE 1024 -LOG The Modicon DAS uses a different Application Profile ID for each programmable controller family that it supports. When defining a VMD, be sure to specify the proper protocol profile for the family of programmable controller being defined. The MAXPDUSIZE should be greater than or equal to the largest total packet sent by the device. If a packet is segmented into several smaller packets use the total packet size for this number. 2.3.1.3 Editing VMD Definitions The VMD definition represents an Modicon device and references previously defined ODS and protocol profile definitions. Example 2-3 shows the configuration file commands that create VMD definitions. Example 2-3 VMD Configuration (continued on next page) and Configuring the DAS for Modicon Programmable Controllers 2-15 Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Example 2-3 (Cont.) VMD Configuration CREATE VMD mod_984 -MODEL "Modicon_984" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD984_PATH":mod_984 \ -DESCRIPTION "Modicon 984 programmable controller" \ -LOG CREATE VMD modplus_984_slave -MODEL "Modicon_984" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MODPLUS984_SLAVE_PATH":modplus_984 \ -DESCRIPTION "Modicon 984 programmable controller" \ -LOG CREATE VMD modplus_984_node -MODEL "Modicon_984" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MODPLUS984_NODE_PATH":modplus_984 \ -DESCRIPTION "Modicon SQ/SA-85 card" \ -LOG CREATE VMD mod_884 -MODEL "Modicon_884" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD884_PATH":mod_884 \ -DESCRIPTION "Modicon 884 programmable controller" \ -LOG CREATE VMD mod_584 -MODEL "Modicon_584" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD584_PATH":mod_584 \ -DESCRIPTION "Modicon 584 programmable controller" \ -LOG CREATE VMD mod_484 -MODEL "Modicon_484" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD484_PATH":mod_484 \ -DESCRIPTION "Modicon 484 programmable controller" \ -LOG An access point is created using the following syntax: APPLICATION_SIMPLE_NAME:PROTOCOL_PROFILE_NAME. The APPLICATION_SIMPLE_NAME is the definition registered in ODS. The PROTOCOL_PROFILE_NAME is defined using the BASEstar Open CLI as described in Section 2.3.1.2. An access point tells the BASEstar Open software how to access the VMD. For more information on specifying client and DVM access points, refer to BASEstar Open for OpenVMS Command Language Interface. 2-16 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Modify the command for your site configuration. Table 2-4 lists the modifiable device attributes. and Configuring the DAS for Modicon Programmable Controllers 2-17 Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Table_2-4_VMD_CREATE_______________________________________ Parameter_____________Modifiable?_Value(s)_________________ MODEL Yes[1] Programmable controller model VENDOR Yes[1] Modicon REVISION Yes[1] CLIENT_ACCESS_POINT Yes[2] DVM_ACCESS_POINT Yes[2] DESCRIPTION Yes[1] Descriptive text [1]The_value_of_this_field_is_informational_only_and_is_not checked by the DAS. [2]See the BASEstar Open for OpenVMS Command Language Interface for information on specifying client and DVM access points. ___________________________________________________________ 2-18 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks 2.3.1.4 DAS for Modicon Programmable Controllers Configuration Files Example 2-4 and Example 2-5 are samples of the ODS and BSTR configuration files for the DAS for Modicon programmable controllers. Example 2-4 DAS for Modicon Programmable Controllers ODS Configuration File $ ! $ !********************************************************************! $ ! ! $ ! This is a template for the Modicon-specific ! $ ! ODS configuration command file. Rename and edit this command ! $ ! procedure template to reflect your site-specific ! $ ! configuration. You must manually execute this command ! $ ! procedure to configure ODS to provide line configuration ! $ ! information for your devices. ! $ ! ! $ ! Add comments to the site-specific changes here. ! $ ! ! $ !********************************************************************! $ ! $ODSCL := $ODS:[EXE]ODSCL.EXE $ ! $ ! Register the ODS definitions. $ ! $ODSCL REGISTER DIRECTORY NAME "/LINE=MODBUS_LINE" ATTRIBUTES "OC=MODBUS_LINE /PORT=LTA207:/RETRIES=3/SPEED=9600/PARITY=none/MODEM=0/TIMEOUT=3/TRACE=0" REGISTER DIRECTORY NAME "/LINE=MODPLUS_LINE" ATTRIBUTES "OC=MODPLUS_LINE /PORT=MPA1:/RETRIES=2/TIMEOUT=2/TRACE=0" (continued on next page) and Configuring the DAS for Modicon Programmable Controllers 2-19 Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Example 2-4 (Cont.) DAS for Modicon Programmable Controllers ODS Configuration File REGISTER DIRECTORY NAME "/PATH=MOD984_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=20" REGISTER DIRECTORY NAME "/PATH=MODPLUS984_SLAVE_PATH" ATTRIBUTES "OC=MODPLUS_SLAVE_PATH/LINE_NAME=(/LINE=MODPLUS_LINE) /SLAVE_ROUTING=03.00.00.00.00/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MODPLUS984_NODE_PATH" ATTRIBUTES "OC=MODPLUS_NODE_PATH/LINE_NAME=(/LINE=MODPLUS_LINE)/NODE_ADDRESS=4/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MOD884_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=21/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MOD584_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=22/TRACE=0" REGISTER DIRECTORY NAME "/PATH=MOD484_PATH" ATTRIBUTES "OC=MODBUS_PATH /LINE_NAME=(/LINE=MODBUS)/SLAVE_ADDRESS=23/TRACE=0" EXIT To execute the ODS command file, enter the following command at the user prompt: @ODS:[SCRIPTS]ODS_MOD_CONFIG.TEMPLATE 2-20 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Example 2-5 DAS for Modicon Programmable Controllers BSTR Configuration File ! ! Create the protocol profile definitions for the Modicon Micro84, ! Modicon 184, Modicon 384, Modicon 484, Modicon 584, Modicon 884, ! and Modicon 984 family of programmable controllers. ! Protocol profile IDs are assigned by DEComni Engineering ! and uniquely identify protocol support to DEComni. ! CREATE PROTOCOL_PROFILE mod_m84 -APPLPROFID 101 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_184 -APPLPROFID 102 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_384 -APPLPROFID 103 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_484 -APPLPROFID 104 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_584 -APPLPROFID 105 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_884 -APPLPROFID 106 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE mod_984 -APPLPROFID 107 -MAXPDUSIZE 1024 -LOG CREATE PROTOCOL_PROFILE modplus_984 -APPLPROFID 108 -MAXPDUSIZE 1024 -LOG ! ! Create VMD definitions. ! Use the ODS entries and protocol profile names created earlier. ! CREATE VMD mod_984 -MODEL "Modicon_984" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD984_PATH":mod_984 \ -DESCRIPTION "Modicon 984 programmable controller" \ -LOG CREATE VMD modplus_984_slave -MODEL "Modicon_984" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MODPLUS984_SLAVE_PATH":modplus_984 \ -DESCRIPTION "Modicon 984 programmable controller" \ -LOG CREATE VMD modplus_984_node -MODEL "Modicon_984" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MODPLUS984_NODE_PATH":modplus_984 \ -DESCRIPTION "Modicon SQ-85 card" \ -LOG CREATE VMD mod_884 -MODEL "Modicon_884" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD884_PATH":mod_884 \ -DESCRIPTION "Modicon 884 programmable controller" \ -LOG (continued on next page) and Configuring the DAS for Modicon Programmable Controllers 2-21 Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Example 2-5 (Cont.) DAS for Modicon Programmable Controllers BSTR Configuration File CREATE VMD mod_584 -MODEL "Modicon_584" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD584_PATH":mod_584 \ -DESCRIPTION "Modicon 584 programmable controller" \ -LOG CREATE VMD mod_484 -MODEL "Modicon_484" \ -VENDOR "Modicon" \ -DVM_ACCESS_POINT "/PATH=MOD484_PATH":mod_484 \ -DESCRIPTION "Modicon 484 programmable controller" \ -LOG ! ! Create actors/activities for the VMDs ! CREATE NODE mod_node -PHYSICAL "your_node" -LOG CREATE DOMAIN /mod_984 CREATE DOMAIN /modplus_984_slave CREATE DOMAIN /modplus_984_node CREATE DOMAIN /mod_884 CREATE DOMAIN /mod_584 CREATE DOMAIN /mod_484 CREATE ACTOR /mod -LOG SET CONTEXT /mod CREATE PROGRAM mod_server -PROGRAM_KIND DATADEV -LOG CREATE PROGRAM modplus_server -PROGRAM_KIND DATADEV -LOG CREATE ACTIVITY modbus_984 -PROGRAM mod_server \ -NODES (mod_node) \ -DOMAINS (/mod_984) \ -VMDS (mod_984) \ -LOG CREATE ACTIVITY modplus_984_slave -PROGRAM modplus_server \ -NODES (mod_node) \ -DOMAINS (/modplus_984_slave) \ -VMDS (modplus_984_slave) \ -LOG CREATE ACTIVITY modplus_984_node -PROGRAM modplus_server \ -NODES (mod_node) \ -DOMAINS (/modplus_984_node) \ -VMDS (modplus_984_node) \ -LOG (continued on next page) 2-22 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Example 2-5 (Cont.) DAS for Modicon Programmable Controllers BSTR Configuration File CREATE ACTIVITY modbus_884 -PROGRAM mod_server \ -NODES (mod_node) \ -DOMAINS (/mod_884) \ -VMDS (mod_884) \ -LOG CREATE ACTIVITY modbus_584 -PROGRAM mod_server \ -NODES (mod_node) \ -DOMAINS (/mod_584) \ -VMDS (mod_584) \ -LOG CREATE ACTIVITY modbus_484 -PROGRAM mod_server \ -NODES (mod_node) \ -DOMAINS (/mod_484) \ -VMDS (mod_484) \ -LOG To execute the BASEstar Open command file, enter the following command at the user prompt: $CLI_BSTR -F BSTR_MOD_CONFIG.TEMPLATE For more information about maintaining protocol profile and device definitions, refer to the BASEstar Open for OpenVMS Command Language Interface. For more information about maintaining ODS definitions, refer to the DEComni for OpenVMS Guide to Using Omni Directory Services. 2.3.2 Configuring Ports You can physically connect a device to a Local Area Transport (LAT) port. To use a LAT port with the DAS, you must define the LAT port on the OpenVMS system using the LAT control program. For example, to define port_2 on the LAT node srvr4 as LTA992, enter the following: $ MCR LATCP LCP> CREATE PORT LTA992 LCP> SET PORT LTA992 /NODE=srvr4/PORT=port_2/NOQUEUE Use the LAT port name defined above when defining the port to ODS. and Configuring the DAS for Modicon Programmable Controllers 2-23 Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks You must also set the following SYSGEN parameters to access Modicon programmable controllers 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 Utilities Reference Manual for details. ___________________________________________________________ Parameter________Value_____________________________________ TTY_ALTALARM 0 TTY_ALTYPAHD_____512_______________________________________ To enable use of the alternate typeahead buffer, type the following command from DCL: $ SET TERM LTA992:/ALTYPEAHD/PERMANENT For the DAS for Modicon programmable controllers to send and receive data correctly, you must set and define LAT port characteristics to match the line parameters defined in ODS for the corresponding port. The following example shows the characteristics set at the LAT prompt: 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 EVEN 2.3.3 Setting Up Plant-Floor Equipment To set up your plant-floor equipment, refer to the Modicon documentation for your specific device. 2.3.4 Tracing Device Communications The DAS for Modicon programmable controllers has built into it the capablity to trace device communications and to send this output to either a file or to a user terminal. The purpose of this tracing is to allow the troubleshooting of device communications. 2-24 Installing and Configuring the DAS for Modicon Programmable Controllers Installing and Configuring the DAS for Modicon Programmable Controllers 2.3 Postinstallation Tasks Tracing can be enabled for a device and/or a line. If tracing is enabled for a device, then only communications from/to that device are traced. If tracing is enabled for a line, then all communications from/to that line are traced. If both device and line tracing is enabled, then the trace will contain the output for both the device and the line, so the trace output will be duplicated. To enable tracing do the following: o Set the TRACE attribute in the ODS definition for the path or line being traced. o Set the DAS_TRACE_OUTPUT logical name to the name of the file that you want to contain the trace output. The logical name must be defined in a scope that will be seen by the server the DAS is a part of. DEFINE DAS_TRACE_OUTPUT TRACE_OUTPUT.LOG o Reinitiate communications to the device/line. The ODS definition is read when a connection to the device is initiated (device tracing) or when a connection to the line is initiated (line tracing), so communications must be reinitiated in order for tracing to occur. The trace output is flushed to the file after every 10 lines that are traced, so trace output may lag actual device I/O. All trace output is in hexadecimal and shows both input to and output from the device. To turn tracing off, reverse the steps used to turn tracing on. 2.4 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 and Configuring the DAS for Modicon Programmable Controllers 2-25 Installing and Configuring the DAS for Modicon Programmable Controllers 2.4 Failures During Product Use 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 Open you are using - The hardware system you are using (such as a model number) - The Modicon programmable controllers 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. 4. Report only one problem per SPR. This will facilitate a faster response. 5. Mail the SPR package to Digital. 2-26 Installing and Configuring the DAS for Modicon Programmable Controllers 3 _________________________________________________________________ Using the DAS for Modicon Programmable Controllers This chapter provides information about the supported functions for Modicon devices, and how to access these functions. 3.1 Accessing Modicon Functions DAS for Modicon programmable controllers functions are accessed through the following interfaces: o BASEstar Open Command Language Interface (CLI) o BASEstar Open Application Programming Interface (API) o DEComni Application Programming Interface (API) Command Language Interface (CLI) To access the BASEstar Open CLI, enter the following command at the DCL prompt ($): $ CLI_BSTR For information about BASEstar Open commands, refer to the BASEstar Open for OpenVMS Command Language Interface. Application Programming Interface (API) For information on accessing DEComni Callable Services, refer to the DEComni for OpenVMS Application Programmer's Interface. 3.2 Supported Functions A variety of functions are supported by the DAS for Modicon programmable controllers. These functions may be supported as either client or server or both. If a function is supported as a server, then the application will receive an indication when the VMD is requesting the service. Using the DAS for Modicon Programmable Controllers 3-1 Using the DAS for Modicon Programmable Controllers 3.2 Supported Functions The Modicon DAS supports the following client functions for all supported devices: o Connect o Read Variable o Write Variable o Abort o Conclude The Modicon DAS supports the following server functions (indications) for all supported devices: o Info Report o Abort 3.2.1 Connect, Conclude and Abort Functions Table 3-1 lists the connect, conclude and abort functions available through the DEComni (API) interface. Table_3-1_Connect,_Conclude_and_Abort_Interface_Access_____ Interface___Function_Name__________________________________ API omni_connect omni_connect_a omni_conclude omni_conclude_a omni_abort ____________omni_abort_a___________________________________ 3.2.2 Read and Write Variable Functions Use the read variable and write variable functions to read data from and write data to a specific address in device memory. 3-2 Using the DAS for Modicon Programmable Controllers Using the DAS for Modicon Programmable Controllers 3.2 Supported Functions Table 3-2 lists the variable types supported by this DAS. Table_3-2_Read_and_Write_Variable_Types____________________ Variable_Type_________Address_Type__________Supported______ UNNAMED_VARIABLE NUMERIC Yes SYMBOLIC No UNCONSTRAINED Yes[1] NAMED_VARIABLE Yes[2] [1]Unconstrained_addresses_must_be_used_for_Modicon_584_and 984 extended addresses. Unconstrained addresses must also be used for Modicon 984 coil addresses of 010000 or higher to distinguish them from discrete input addresses. [2]Named variables are not supported by the DAS, but they are used by BASEstar Open when accessing variables using the Device Manager Server. The BASEstar Open Device Manager Server converts named variables with an address type of UNCONSTRAINED to unnamed variables. ___________________________________________________________ An UNNAMED_VARIABLE type describes a specific physical address on a VMD. This address has a predefined type based on the address. Variables of this type are an inherent part of the VMD architecture and are uniquely identified by their physical address. An unnamed variable can be one of the following types: o NUMERIC A numeric address must be an MMS unsigned integer. o SYMBOLIC A symbolic address must be an MMS visible string. o UNCONSTRAINED An unconstrained address can be any MMS octet (byte) string. A NAMED_VARIABLE type describes a variable on a device. Variables of this type are uniquely identified by their name. Using the DAS for Modicon Programmable Controllers 3-3 Using the DAS for Modicon Programmable Controllers 3.2 Supported Functions Table 3-3 lists the read and write variable functions available through the BASEstar Open (CLI) and DEComni (API) interfaces. Table_3-3_Read_and_Write_Variable_Interface_Access_________ Interface___Function_Name__________________________________ CLI GET VALUE UNNAMED_VARIABLE GET VALUE NAMED_VARIABLE PUT VALUE UNNAMED_VARIABLE PUT VALUE NAMED_VARIABLE API omni_get_value omni_get_value_a omni_put_value ____________omni_put_value_a_______________________________ Example 3-1 shows examples of creating unnamed variables using the CREATE UNNAMED_VARIABLE command. Example 3-1 UNNAMED_VARIABLE CREATE Command (continued on next page) 3-4 Using the DAS for Modicon Programmable Controllers Using the DAS for Modicon Programmable Controllers 3.2 Supported Functions Example 3-1 (Cont.) UNNAMED_VARIABLE CREATE Command BSTR> CREATE UNNAMED_VARIABLE mod_184.p1 \ -DATATYPE INTEGER_16 \ -ADDRESS "4001" \ -ADDRTYPE NUMERIC BSTR> CREATE UNNAMED_VARIABLE mod_384.p1 \ -DATATYPE INTEGER_16 \ -ADDRESS "4001" \ -ADDRTYPE NUMERIC BSTR> CREATE UNNAMED_VARIABLE mod_584.p1 \ -DATATYPE BIT \ -ADDRESS "1" \ -ADDRTYPE NUMERIC BSTR> CREATE ARRAY_DATATYPE WORD_ARRAY_10 \ -DATATYPE INTEGER_16 \ -SIZE 10 BSTR> CREATE UNNAMED_VARIABLE mod_584.p2 \ -DATATYPE WORD_ARRAY_10 \ -ADDRESS "40001" \ -ADDRTYPE NUMERIC BSTR> CREATE UNNAMED_VARIABLE mod_884.p1 \ -DATATYPE BIT \ -ADDRESS "10001" \ -ADDRTYPE NUMERIC BSTR> CREATE UNNAMED_VARIABLE mod_984.p1 \ -DATATYPE INTEGER_16 \ -ADDRESS "60001:1" \ -ADDRTYPE UNCONSTRAINED BSTR> CREATE UNNAMED_VARIABLE mod_984.p2 \ -DATATYPE INTEGER_16 \ -ADDRESS "40001" \ -ADDRTYPE NUMERIC Using the DAS for Modicon Programmable Controllers 3-5 Using the DAS for Modicon Programmable Controllers 3.2 Supported Functions Example 3-2 shows the information displayed when you enter the GET VALUE UNNAMED_VARIABLE command. Example 3-2 UNNAMED_VARIABLE DISPLAY_VALUE Output BSTR> GET VALUE UNNAMED_VARIABLE mod_184.p1 20 BSTR> GET VALUE UNNAMED_VARIABLE mod_384.p1 10 BSTR> GET VALUE UNNAMED_VARIABLE mod_584.p1 0 BSTR> GET VALUE UNNAMED_VARIABLE mod_584.p2 array[10] of INTEGER_16 [ 0]: 0 [ 1]: 0 [ 2]: 0 [ 3]: 0 [ 4]: 0 [ 5]: 0 [ 6]: 0 [ 7]: 0 [ 8]: 0 [ 9]: 0 BSTR> GET VALUE UNNAMED_VARIABLE mod_884.p1 1 BSTR> GET VALUE UNNAMED_VARIABLE mod_984.p1 30 BSTR> GET VALUE UNNAMED_VARIABLE mod_984.p2 40 Example 3-3 shows the information displayed when you enter the PUT VALUE UNNAMED_VARIABLE command. Example 3-3 UNNAMED_VARIABLE MODIFY_VALUE Output (continued on next page) 3-6 Using the DAS for Modicon Programmable Controllers Using the DAS for Modicon Programmable Controllers 3.2 Supported Functions Example 3-3 (Cont.) UNNAMED_VARIABLE MODIFY_VALUE Output BSTR> PUT VALUE UNNAMED_VARIABLE mod_584.p1 (Bit) : 1 BSTR> PUT VALUE UNNAMED_VARIABLE mod_584.p2 array[10] of INTEGER_16 [ 0]: (Integer 16) : 1 [ 1]: (Integer 16) : 2 [ 2]: (Integer 16) : 3 [ 3]: (Integer 16) : 4 [ 4]: (Integer 16) : 5 [ 5]: (Integer 16) : 6 [ 6]: (Integer 16) : 7 [ 7]: (Integer 16) : 8 [ 8]: (Integer 16) : 9 [ 9]: (Integer 16) : 10 3.2.3 Information Report and Abort Indications An indication is data that is sent to the DAS from the device without the DAS specifically requesting the data. The DAS supports information report and abort indications. The information report indication is used when the device is sending data to the host. Information reports are only supported for Modbus-Plus which supports peer-to-peer communications. With Modbus-Plus, the host can receive slave commands as well as issue master commands. In order to use the info report function, a variable must be created on the host that matches the address and size of the data being sent by the programmable controller. If a programmable controller has been programmed to send data to the host and a variable is found that matches the address of the data being sent, an info report indication is generated specifying the variable that was found. If more than one variable is configured that matches the address of the data being sent, then an indication is generated only for the first variable found. When programming the programmable controller to send data to the host, use the special master function (MSTR) block with the write data function code (1). Using the DAS for Modicon Programmable Controllers 3-7 Using the DAS for Modicon Programmable Controllers 3.2 Supported Functions The DAS supports writing from the programmable controller to the host only. Reads from the programmable controller to the host are not currently supported. An abort indication is generated by the DAS when it loses a connection to the device. The DAS detects that a connection is broken when an error is returned from a QIO call. In this case all connections using this port are aborted. Table 3-4 lists the indication functions available through the DEComni (API) interface. Table_3-4_Indication_Interface_Access______________________ Interface___Function_Name__________________________________ API omni_get_indications ____________omni_get_indications_a_________________________ 3.3 Addressing Syntax and Supported Data Types Data types are defined at the device and application levels. The device data type is referred to as the MMS data type. The MMS data type is mapped to an application data type. Data types can be either simple or complex. Simple data types are native to the DEComni environment. Complex data types are divided into either arrays or structures. Complex data types must be created by a user before they can be used in defining data points or variables. Structures are not supported for the DAS for Modicon programmable controllers. The following sections describe the supported data types and addressing syntax for each of the supported device families. 3-8 Using the DAS for Modicon Programmable Controllers Using the DAS for Modicon Programmable Controllers 3.3 Addressing Syntax and Supported Data Types 3.3.1 Modicon Micro 84 Addressing Syntax and Supported Data Types Table 3-5 shows the structure of a legal address for the Micro 84 family. Table_3-5_Modicon_Micro_84_Address_Format__________________ Address_Format___MMS_Type[1]______Description______________ 0001 - 0064 BIT Coils 1001 - 1064[2] BIT Discrete inputs 3001 - 3004[2] UNSIGNED_16 Input registers INTEGER_16 4001 - 4032 UNSIGNED_16 Holding registers INTEGER_16 [1]Arrays_are_supported._Variable_size_arrays_are_not______ supported. [2]Writes are not supported. ___________________________________________________________ 3.3.2 Modicon 184 and 384 Addressing Syntax and Supported Data Types Table 3-6 shows the structure of a legal address for the Modicon 184 and 384 families. Table_3-6_Modicon_184_and_384_Address_Format_______________ Address_Format___MMS_Type[1]______Description______________ 0001 - 0992 BIT Coils 1001 - 1992[2] BIT Discrete inputs 3001 - 3999[2] UNSIGNED_16 Input registers INTEGER_16 4001 - 4999 UNSIGNED_16 Holding registers INTEGER_16 [1]Arrays_are_supported._Variable_size_arrays_are_not______ supported. [2]Writes are not supported. ___________________________________________________________ Using the DAS for Modicon Programmable Controllers 3-9 Using the DAS for Modicon Programmable Controllers 3.3 Addressing Syntax and Supported Data Types 3.3.3 Modicon 484 Addressing Syntax and Supported Data Types Table 3-7 shows the structure of a legal address for the Modicon 484 family. Table_3-7_Modicon_484_Address_Format_______________________ Address_Format___MMS_Type[1]______Description______________ 0001 - 0512 BIT Coils 1001 - 1256[2] BIT Discrete inputs 3001 - 3032[2] UNSIGNED_16 Input registers INTEGER_16 4001 - 4254 UNSIGNED_16 Holding registers INTEGER_16 [1]Arrays_are_supported._Variable_size_arrays_are_not______ supported. [2]Writes are not supported. ___________________________________________________________ 3.3.4 Modicon 884 Addressing Syntax and Supported Data Types Table 3-8 shows the structure of a legal address for the Modicon 884 family. Table_3-8_Modicon_884_Address_Format_______________________ Address_Format___MMS_Type[1]______Description[3]___________ 00001 - 00768 BIT Coils 10001 - BIT Discrete inputs 10256[2] 30001 - UNSIGNED_16 Input registers 30256[2] INTEGER_16 40001 - 40864 UNSIGNED_16 Holding registers INTEGER_16 [1]Arrays_are_supported._Variable_size_arrays_are_not______ supported. [2]Writes are not supported. [3]Sequencer registers, double precision registers and latches are not supported. ___________________________________________________________ 3-10 Using the DAS for Modicon Programmable Controllers Using the DAS for Modicon Programmable Controllers 3.3 Addressing Syntax and Supported Data Types 3.3.5 Modicon 584 and 984 Addressing Syntax and Supported Data Types Table 3-9 shows the structure of a legal address for the Modicon 584 and 984 families. Table_3-9_Modicon_584_and_984_Address_Format_______________ Address_Format___MMS_Type[1]______Description______________ 00001 - 08192 BIT Coils 10001 - BIT Discrete inputs 18192[2] 30001 - UNSIGNED_16 Input registers 39999[2] INTEGER_16 40001 - 49999 UNSIGNED_16 Holding registers INTEGER_16 60000:1 - UNSIGNED_16 Extended file 69999:10[3] INTEGER_16 000001 - BIT Coils 065535[4] 100001 - BIT Discrete inputs 116384[2] 300001 - UNSIGNED_16 Input registers 365535[2] INTEGER_16 400001 - 465535 UNSIGNED_16 Holding registers INTEGER_16 FLOAT 600000:1 - UNSIGNED_16 Extended file 665535:10[3] INTEGER_16 [1]Arrays_are_supported._Variable_size_arrays_are_not______ supported. [2]Writes are not supported. [3]If a file number is not specified, then the file number defaults to 1. [4]Six digit addresses are supported for Modicon 984's only. To specify a coil 010000 or above, use an unconstrained address, not a numeric address, in order to distinguish the address from a discrete input. ___________________________________________________________ Using the DAS for Modicon Programmable Controllers 3-11 A _________________________________________________________________ Error Messages This appendix contains returned values and associated error messages specific to the DAS for Modicon programmable controllers. aborting, The connection to the device is being aborted, Explanation: Error. The connection to the device is being aborted by an error or by user request. No more requests will be processed by the DAS until the connection is restored. User Action: If the abort was caused by a device error, take action based on the error that occurred. If the abort was a result of a user request. Reconnect to the device before attempting further operations. addresstoolong, Variable address string too long, Explanation: Error. A variable address that is being defined is too long. An address must be 30 characters of less in length. User Action: Redefine the variable using a shorter address. allocerror, An error occurred when allocating an OpenVMS port, Explanation: Error. An error occurred when allocating an OpenVMS port. The allocation is done when a connection is initiated with the VMD. User Action: An error message detailing the error should have been logged. Examine the error to determine the proper corrective action. Error Messages A-1 Error Messages allocplusstatus, Status for line XX and path X returned from SYS$QIOW | IO$_ALLOC, XX, Explanation: Error. An error occurred when allocating a Modbus Plus path. If the path number is greater than 0 then at least one path was allocated to process Modbus Plus messages. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. allocstatus, Status for line XX returned from SYS$ALLOC, XX, Explanation: Error. An error occurred when allocating a port. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. apptypeunsupp, The given application type is not supported for this DAS, Explanation: Error. The application type that was specified in the variable definition is not supported by this DAS. User Action: Change the application type to a valid type for this DAS. assignerror, An error occurred when assigning a channel to an OpenVMS port, Explanation: Error. An error occurred when assigning a channel to an OpenVMS port. The assignment is done when a connection is initiated with the VMD. User Action: An error message detailing the error should have been logged. Examine the error to determine the proper corrective action. assignplusstatus, Status for line XX and path X returned from SYS$ASSIGN, XX, Explanation: Error. An error occurred when assigning a channel to a Modbus Plus path. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. A-2 Error Messages Error Messages assignstatus, Status for line XX returned from SYS$ASSIGN, XX, Explanation: Error. An error occurred when assigning a channel. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. badaddress, VMD XX receieved data for address X, but this address does not exist on the host, Explanation: Error. A variable was received from a programmable controller and the address did not match any variables defined on the host VMD. User Action: Define a variable with the correct address on the host VMD or change the address of the variable being sent from the programmable controller. datatoosmall, Programmable controller data too small for the data size of the variable, Explanation: Error. A variable was received from a programmable controller and the address matched a host variable, but the size of the data defined for the variable is larger than the size of the data actually received. User Action: Define a variable with the correct size as the data being sent or change the size of the data being sent by the programmable controller. devfailed, Failure in associated device, Explanation: Error. The slave's programmable controller has failed to respond to a message or an abortive error occurred. User Action: An irrecoverable error in the programmable controller occurred. Replace or repair the defective programmable controller. devilladdress, Illegal data address, Explanation: Error. The address referenced in the data field is not an allowable address for the addressed slave location. User Action: Check the model of the programmable controller and the documentation to determine a valid address for the Error Messages A-3 Error Messages programmable controller. Then modify the address to a valid address for this programmable controller. devillegalfnc, Illegal function, Explanation: Error. The message function received is not an allowable action for the addressed slave. This error is most likely caused by setting an incorrect application profile, so a command is being sent to a wrong model programmable controller. User Action: Check that the corrrect application profile is being used for this model of programmable controller. devillvalue, Illegal data value, Explanation: Error. The value referenced in the data field is not an allowable value for this addressed slave location. User Action: Check the model of the programmable controller and the documentation to determine a valid value for the programmable controller. Then modify the value to a valid value for this programmable controller. disconnerror, An error occurred when assigning a disconnect AST to a port, Explanation: Error. An error occurred when assigning a disconnect AST to an OpenVMS port. The disconnect AST allows the DAS to determine if the LAT port has been disconnected and to to abort communications with the VMD. User Action: An error message detailing the error should have been logged. Examine the error to determine the proper corrective action. disconnstatus, Status for line XX returned from SYS$QIOW (IO$_ SETMODE | IO$M_CTRLYAST), XX, Explanation: Error. An error occurred when requesting a disconnect AST from a LAT port. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. internalerror, Internal error, Explanation: Error. An internal error occurred in the DAS. User Action: Submit an SPR describing the circumstances that caused the error. A-4 Error Messages Error Messages invaddresstype, Invalid address type, Explanation: Error. A variable that is being defined is defined as an illegal address type. The unconstrained address type is used for Modicon 584 and 984 extended files. The numeric address type is used for all other registers /coils. User Action: Redefine the variable using the proper unconstrained or numeric address type. invalidaddress, The specified programmable controller address is not supported by this DAS, Explanation: Error. An address was sent by a programmable controller but the address is not supported by this DAS. User Action: Reprogram the programmable controller and specify a valid address for this DAS. Consult the DAS documentation to determine a valid address. invalidfunction, Invalid function code received in a message from the programmable controller, Explanation: Error. A message was received from the programmable controller, but the function code used by the programmable controller in the write command is not supported by the DAS. User Action: Reprogram the programmable controller to send the correct function code. invalidmodem, Invalid modem attribute specified in the MODBUS_ LINE ODS entry, Explanation: Error. The modem attribute must be one of TRUE, ON, YES, 1 or FALSE, OFF, NO, 0. User Action: Use ODS to enter a valid modem attribute. invalidnodeaddress, Invalid node address number in the MODPLUS_ NODE_PATH ODS entry, Explanation: Error. Modbus node address numbers must be a number between 1-64. The node address is a DIP switch setting on your Modbus Plus card. User Action: Use ODS to enter a node address number between 1-64. Make sure the address matches the DIP switch setting on the Modbus Plus card. Error Messages A-5 Error Messages invalidparity, Invalid parity specified in the MODBUS_LINE ODS entry, Explanation: Error. The parity defined must be either EVEN, ODD or NONE. User Action: Use ODS to enter a valid parity (EVEN, ODD, NONE). invalidport, Invalid port name specified in the ODS entry, Explanation: Error. Port names must be 10 characters or less. User Action: Use ODS to enter a port name that is less than 10 characters. invalidretries, Invalid retries number in the ODS entry, Explanation: Error. The retries attribute must be between 0-20. User Action: Use ODS to enter a retries number between 0-20. invalidslaveaddress, Invalid slave address number in the MODBUS_PATH ODS entry, Explanation: Error. Modbus slave address numbers must be a number between 1-247. User Action: Use ODS to enter a slave address number between 1-247. invalidslavepath, Invalid slave routing path in the MODPLUS_ SLAVE_PATH ODS entry, Explanation: Error. Modbus Plus routing paths are of the form xx.xx.xx.xx.xx. Nodes must be in the range 1-64. If using a multiplexor bridge to a networked Modbus slave device the last routing byte can be 1-247. All five bytes must be specified. Unused routing bytes must be 0. User Action: Use ODS to enter a slave routing path with the proper syntax and valid node/slave address numbers. invalidspeed, Invalid speed (baud rate) specified in the MODBUS_LINE ODS entry, Explanation: Error. Baud rates from 110 to 19200 are supported for the Modicon DAS. User Action: Use ODS to enter a speed from 110 to 19200. A-6 Error Messages Error Messages invalidtimeout, Invalid timeout value in the ODS entry, Explanation: Error. An invalid timeout value was entered for the timeout value in ODS. Timeouts must be between 2 and 10 seconds. User Action: Use ODS to enter a timeout value between 2-10. invalidtrace, Invalid trace attribute specified in the MODBUS_ LINE or MODBUS_PATH ODS entry, Explanation: Error. The trace attribute must be one of TRUE, ON, YES, 1 or FALSE, OFF, NO, 0. User Action: Use ODS to enter a valid trace attribute. latcode, Status for line XX returned from SYS$QIOW (IO$_TTY_ PORT | IO$M_LT_CONNECT) = X, Explanation: Error. An error occurred when connecting to a LAT port. User Action: Examine the error code to determine the cause of the error and take appropriate action based on the error code. laterror, An error occurred when connecting to a LAT port, Explanation: Error. An error occurred when connecting to a LAT port. The connection is done when a connection is initiated with the VMD. User Action: An error message detailing the error should have been logged. Examine the error to determine the proper corrective action. latmodeminv, Invalid attempt to enable modem signals on a LAT port, Explanation: Error. LAT ports do not support setting of the "modem" ODS parameter to "TRUE". User Action: Change the port to a non-LAT port or change the "modem" parameter to "FALSE", "0" or "OFF". Error Messages A-7 Error Messages latstatus, Status for line XX returned from SYS$QIOW (IO$_TTY_ PORT | IO$M_LT_CONNECT), XX, Explanation: Error. An error occurred when connecting to a LAT port. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. maxlines, The maximum number of lines have already been configured, Explanation: Error. The maximum number of lines have already been for this system. A maximum of four Modbus Plus cards can be configured for one VAX. User Action: Reconfigure the /LINE_NAME parameter to match a valid configuration for this system. mmsaddrtypeunsupp, The given MMS type is unsupported for the given address, Explanation: Error. The MMS type is not supported for the variable address given. User Action: Modify the MMS type to one supported for the given address or modify the address to one supported for the MMS type. mmstypeunsupp, The given MMS type is not supported for this DAS, Explanation: Error. The MMS type that was specified in the variable definition is not supported by by this DAS. User Action: Change the MMS type to a valid type for this DAS. modbuserror, A modbus error occurred, Explanation: Error. A Modbus error occurred when reading or writing to the programmable controller. User Action: Retry issuing the command. A-8 Error Messages Error Messages neterr, Modbus network error occurred, Explanation: Error. A network error on the Modicon Modbus occurred. User Action: Examine the network status in the returned IOSB to determine the specific network error that occurred and take action based on that error. noaddress, No "NODE_ADDRESS" or "SLAVE_ROUTING" ODS entry for the given application simple name, Explanation: Error. The Modicon DAS requires a NODE_ADDRESS or SLAVE_ROUTING attribute defined for the ODS entry corresponding to the application simple name entry for the VMD. The NODE_ADDRESS attribute is defined for MODPLUS_NODE_ PATH object class within ODS. The SLAVE_ROUTING attribute is defined for the MODPLUS_SLAVE_PATH object class within ODS. User Action: Use the MODPLUS_NODE_PATH or MODPLUS_SLAVE_PATH object class within ODS to define the application simple name for this VMD. Use a valid Modbus Plus node address number if defining the NODE_ADDRESS attribute. Use a valid Modbus Plus slave routing path if defining the SLAVE_ROUTING attribute. nolicense, No software license., Explanation: Error. The Modicon DAS requires a software license. User Action: Install the license PAK for the Modicon DAS. noline, No "/LINE=" ODS entry for the given application simple name, Explanation: Error. The Modicon DAS requires a /LINE= attribute defined for the ODS entry corresponding to the application simple name entry for the remote VMD. The /LINE= attribute is defined for MODBUS_PATH and MODPLUS_SLAVE_PATH object classes within ODS. User Action: Use the MODBUS_PATH object class (for Modbus) or MODPLUS_SLAVE_PATH object class (for Modbus Plus) within ODS to define the application simple name for this VMD. Use a valid line name when defining the /LINE= attribute. Error Messages A-9 Error Messages nomodem, No "MODEM" ODS entry for the given line, Explanation: Error. The Modicon DAS requires a MODEM attribute defined in ODS. The MODEM attribute is defined for the MODBUS_LINE object class within ODS. User Action: Use the MODBUS_LINE object class within ODS to define the MODEM attribute for this line. Modem control is either enabled (TRUE, ON, YES, 1) or disabled (FALSE, OFF, NO, 0). noparity, No "PARITY" ODS entry for the given line, Explanation: Error. The Modicon DAS requires a PARITY attribute defined in ODS. The PARITY attribute is defined for the MODBUS_LINE object class within ODS. User Action: Use the MODBUS_LINE object class within ODS to define the PARITY attribute for this line. Use a valid parity (EVEN, NONE) when defining the PARITY attribute. noport, No "PORT" ODS entry for the given line, Explanation: Error. The Modicon DAS requires a PORT attribute defined in ODS. The PORT attribute is defined for the MODBUS_LINE object class within ODS. User Action: Use the MODBUS_LINE object class within ODS to define the PORT attribute for this line. Use a valid port name when defining the PORT attribute. noretries, No "RETRIES" ODS entry for the given line, Explanation: Error. The Modicon DAS requires a RETRIES attribute defined in ODS. The RETRIES attribute is defined for the MODBUS_LINE object class within ODS. User Action: Use the MODBUS_LINE object class within ODS to define the RETRIES attribute for this line. Use a valid number when defining the RETRIES attribute. noslaveaddress, No "SLAVE_ADDRESS" ODS entry for the given application simple name, Explanation: Error. The Modicon DAS requires a SLAVE_ADDRESS attribute defined for the ODS entry corresponding to the application simple name entry for the remote VMD. The SLAVE_ A-10 Error Messages Error Messages ADDRESS attribute is defined for MODBUS_PATH object class within ODS. User Action: Use the MODBUS_PATH object class within ODS to define the application simple name for this VMD. Use a valid Modbus slave address number when defining the SLAVE_ADDRESS attribute. nospeed, No "SPEED" ODS entry for the given line, Explanation: Error. The Modicon DAS requires a SPEED attribute defined in ODS. The SPEED attribute is defined for the MODBUS_LINE object class within ODS. User Action: Use the DH_LINE object class within ODS to define the SPEED attribute for this line. Use a valid baud rate when defining the SPEED attribute. notimeout, No "TIMEOUT" ODS entry for the given line, Explanation: Error. The Modicon DAS requires a TIMEOUT attribute defined in ODS. The TIMEOUT attribute is defined for the MODBUS_LINE object class within ODS. User Action: Use the MODBUS_LINE object class within ODS to define the TIMEOUT attribute for this line. Use a valid number when defining the TIMEOUT attribute. notrace, No "TRACE" ODS entry, Explanation: Error. The Modicon DAS requires a TRACE attribute defined in ODS. The TRACE attribute is defined for the MODBUS_PATH, MODBUS_LINE, MODPLUS_LINE, MODPLUS_ SLAVE_PATH and MODPLUS_NODE_PATH object classes within ODS. User Action: Use the appropriate object class within ODS to define the TRACE attribute for this line. Trace is either enabled (TRUE, ON, YES, 1) or disabled (FALSE, OFF, NO, 0). parsefailed, The parsing of a variable address failed, Explanation: Error. When defining a variable, the parsing of the address failed. Either the syntax or the value of the address is incorrect. User Action: Consult the user documentation to determine a valid address for the variable being defined and redefine the variable using the correct syntax. Error Messages A-11 Error Messages readerror, Read error on communications line, Explanation: Error. An error was returned when reading from the port. The error is logged separately. User Action: Look up the error and take action based on the error found. reqpending, Conclude rejected because of a pending read/write request, Explanation: Error. The conclude request was rejected because either a read or a write request was currently pending. User Action: Either abort the connection or wait for the current request(s) to complete before retrying the conclude. retriesexceeded, The retry count was exceeded, Explanation: Error. When trying to communicate to the device, the retry count was exceeded. The retry being exceeded means that the message being sent to the device was garbled during transmission and did not match the checksum. User Action: Check cabling to ensure there are no shorts or breaks and is properly grounded. Make sure the cable is routed such that it does not pass close to electrical interference such as transformers and high power cables. smalldata, VMD XX receieved data for address X, but the data was too small, Explanation: Error. A variable was received from a programmable controller and the address matched a host variable, but the size of the data defined for the variable is larger than the size of the data actually received. User Action: Define a variable with the correct size as the data being sent or change the size of the data being sent by the programmable controller. solnotsupported, Solicited operations (read/write) are not supported for this VMD, Explanation: Error. Solicited operations are not supported for this VMD. This VMD is used to receive indications (info reports) from the VMD and is not available to perform read/write operations. The programmable controller did not respond when attempting to read a response from the A-12 Error Messages Error Messages programmable controller. The response could be part of a read or a write operation. User Action: Check all cabling to make sure that it is properly shielded, grounded and seated. Verify that the communication parameters are set up properly on both programmable controller and the host. Verify that the correct slave address has been selected on the programmable controller and on the host. timeout, Modbus timeout when reading from the programmable controller, Explanation: Error. The programmable controller did not respond when attempting to read a response from the programmable controller. The response could be part of a read or a write operation. User Action: Check all cabling to make sure that it is properly shielded, grounded and seated. Verify that the communication parameters are set up properly on both programmable controller and the host. Verify that the correct slave address has been selected on the programmable controller and on the host. tracerddev, XX Trace for device XX - read:, Explanation: Error. Tracing has been enabled for the indicated device. The message is data written to the device. User Action: None. tracerdline, XX Trace for line XX - read:, Explanation: Error. Tracing has been enabled for the indicated line. The message is data read from the line. User Action: None. tracewrdev, XX Trace for device XX - write:, Explanation: Error. Tracing has been enabled for the indicated device. The message is data written to the device. User Action: None. tracewrline, XX Trace for line XX - write:, Explanation: Error. Tracing has been enabled for the indicated line. The message is data written to the line. User Action: None. Error Messages A-13 Error Messages ttcharerror, An error occurred when defining TT characteristics, Explanation: Error. An error occurred when setting up TT characteristics. The TT characteristics are set when a connection is initiated with the VMD. User Action: An error message detailing the error should have been logged. Examine the error to determine the proper corrective action. unexpfunction, Unexpected function received from programmable controller XX. received function code was 'XX', Explanation: Error. An unexpected function code was received in a message from the programmable controller. User Action: Reprogram the programmable controller to send the correct function code. variablenotfound, Variable not found with the specified address, Explanation: Error. A variable was received from a programmable controller and the address did not match any variables defined on the host. User Action: Define a variable with the correct address on the host or change the address of the variable being sent from the programmable controller. vmsioerror, An error occurred when doing I/O to a VMS channel, Explanation: Error. An error occurred when reading or writing to an OpenVMS channel. The channel is assigned to a port used to communicate with the Modbus line. User Action: An error message detailing the error should have been logged. Examine the error to determine the proper corrective action. vmsiostatus, I/O error on line XX, QIO status, XX, Explanation: Error. An error occurred when reading/writing data on an OpenVMS port. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. A-14 Error Messages Error Messages vmsttcharstatus, Status for line XX returned from SYS$QIOW (IO$_SETMODE), XX, Explanation: Error. An error occurred when setting port characteristics. User Action: Examine the error message to determine the cause of the error and take appropriate action based on the error message. writenotsupport, Writes are not supported for the specified address, Explanation: Error. An attempt was made to write to an address that the Modbus protocol does not allow write access to. User Action: Consult the documentation to determine addresses that can be written to and change the address of the variable or only perform reads when using this variable. wrongindication, An indication was received on line XX, Explanation: Error. An inidication was received but a connection has not been established to receive indications on that line. User Action: Establish a connection to receive indications on the line. One VMD on the line is dedicated to receive indications for that line. Error Messages A-15 _________________________________________________________________ Index A______________________________ D______________________________ Abort function, 3-2 DAS Abort indication, 3-7 See Device access software Accessing DAS functions, 3-1 Data types, 3-8 Address syntax, 3-8 Device access software Modicon 184, 3-9 accessing functions, 3-1 Modicon 384, 3-9 address syntax, 3-8 Modicon 484, 3-10 description of, 1-1 Modicon 584, 3-11 functions, 1-2 Modicon 884, 3-10 installation of, 2-1 Modicon 984, 3-11 installation requirements, Modicon Micro 84, 3-9 2-1 C overview, 1-1 _______________________________ supported client functions, CLI 3-2 accessing, 3-1 supported data types, 3-8 Conclude function, 3-2 supported devices, 1-2 Configuration supported functions, 1-2, editing configuration files, 3-1 2-10 supported server functions, ODS registrations, 2-11 3-2 protocol profile, 2-14 using, 3-1 VMD definitions, 2-15 Device communications Configuration files, 2-19 cabling, 2-1 Configuring ports, 2-23 overview, 1-2 Connect function, 3-2 tracing, 2-24 Devices Programmable controllers supported, 1-3 Index-1 Modicon 884 F______________________________ address syntax, 3-10 Files, created during supported data types, 3-10 installation, 2-7 Modicon 984 Functions, 3-1 address syntax, 3-11 abort, 3-2 supported data types, 3-11 conclude, 3-2 Modicon Micro 84 connect, 3-2 address syntax, 3-9 read variable, 3-2 supported data types, 3-9 supported, 3-1 O write variable, 3-2 _______________________________ ODS registrations, 2-11 I______________________________ Indications P______________________________ abort, 3-7 Plant-floor equipment, setting info report, 3-7 up, 2-24 Information report indication, Postinstallation tasks, 2-10 3-7 Problem reporting, 2-25 Installation, 2-1 Product failure, 2-25 files created, 2-7 Protocol profile, 2-14 messages, 2-7 procedure, 2-4 R______________________________ Installation requirements, 2-1 Read variable function, 3-2 disk space, 2-3 hardware, 2-1 S software, 2-3 _______________________________ Supported data types, 3-8 M______________________________ Modicon 184, 3-9 Messages Modicon 384, 3-9 error and return values, A-1 Modicon 484, 3-10 installation, 2-7 Modicon 584, 3-11 MMS data type, 3-8 Modicon 884, 3-10 Modicon 184 Modicon 984, 3-11 address syntax, 3-9 Modicon Micro 84, 3-9 supported data types, 3-9 T Modicon 384 _______________________________ address syntax, 3-9 Trace supported data types, 3-9 ODS configuration, 2-11 Modicon 484 using, 2-24 address syntax, 3-10 supported data types, 3-10 Modicon 584 address syntax, 3-11 supported data types, 3-11 Index-2 V______________________________ VMD definitions, 2-15 W______________________________ Write variable function, 3-2 Index-3