BASEstar[TM] Classic DAS for_DEComni[TM]_Software____________________________ Installation and User's Guide Order Number: AA-R21CA-TE November 1996 This manual describes how to install and use the DAS for DEComni Software 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 Network Software and Version: DEComni/Alpha Version 2.1 Network Software and Version: DEComni/VAX Version 2.0A Software Version: BASEstar Classic DAS for DEComni Software, 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: BASEstar, DECnet, DEComni, DECosap, Digital, OpenVMS, TK, VAX, and the Digital logo. 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 DEComni Software 1.1 Description................................... 1-1 1.2 Device Communications......................... 1-2 1.3 Supported Functions........................... 1-3 1.3.1 Supported MMS Functions................... 1-3 1.3.2 Supported SINEC-AP and SINEC-H1 Functions................................. 1-5 1.4 Non-supported Functions....................... 1-7 2 Installing the DAS for DEComni Software 2.1 Installation Requirements..................... 2-1 2.1.1 Hardware Requirements..................... 2-1 2.1.2 Software Requirements..................... 2-2 2.1.3 Additional Software Requirements.......... 2-2 2.1.4 Disk Space Requirements................... 2-3 2.2 Installing the BASEstar Classic DAS for DEComni Software.............................. 2-4 2.2.1 Files Created During Installation......... 2-10 2.2.2 Installation Messages..................... 2-11 2.3 Post Installation Tasks....................... 2-13 2.3.1 Configuring layered products.............. 2-13 2.3.2 Tuning ILAN$DEVSRV........................ 2-14 2.3.3 Defining DEComni Constants................ 2-15 iii 2.3.4 Editing the Configuration File............ 2-15 2.3.4.1 Editing Type Records.................... 2-15 2.3.4.2 Editing Path Records.................... 2-17 2.3.4.3 Editing Device Records.................. 2-18 2.3.4.4 The DAS for DEComni Software Configuration File Example.............. 2-23 2.3.4.5 NCL Configuration....................... 2-30 2.3.5 DAS SPT Block Usage....................... 2-31 2.3.6 Setting Up Shop Floor Equipment........... 2-32 2.3.7 Tracing OSI Messages...................... 2-32 2.4 Failures During Product Use................... 2-32 3 Using the DAS for DEComni Software 3.1 Accessing DEComni Functions................... 3-1 3.2 Supported Functions........................... 3-2 3.2.1 Connecting To a Device.................... 3-3 3.2.2 Disconnecting a Device.................... 3-3 3.2.3 Read and Write Data Functions............. 3-4 3.2.4 SINEC-AP and SINEC-H1 Read and Write Message functions using ILAN$DEVICE_SPECIFIC...................... 3-9 3.2.5 SINEC-AP Read and Write Message Functions Using Physical Points..................... 3-13 3.2.5.1 Reading a message....................... 3-13 3.2.5.2 Writing a message....................... 3-13 3.2.5.3 Exchanging a message.................... 3-13 3.2.6 Download, Upload and Directory Functions................................. 3-15 3.2.7 Start and Stop Functions.................. 3-17 3.2.8 Read Status Function...................... 3-19 3.2.8.1 Logical Status Meaning.................. 3-19 3.2.8.2 Physical Status Meaning................. 3-20 3.3 Automatic Data Collection..................... 3-21 3.3.1 Unsolicited Data.......................... 3-21 3.3.1.1 Information Report...................... 3-21 3.3.1.2 Write Indication........................ 3-21 3.3.1.3 Read Indication......................... 3-22 3.3.1.3.1 Automatic Reply to Read Indication..... 3-22 3.3.1.3.2 Manual Reply to Read Indication........ 3-23 3.3.1.4 Message Exchange Indication............. 3-24 3.3.1.4.1 Automatic Reply to Exchange Message Indication............................. 3-24 iv 3.3.1.4.2 Manual Reply to Message Exchange Indication............................. 3-25 3.3.1.5 Local and Remote VMDs................... 3-26 3.3.2 Pollsets/Scattered Read................... 3-28 A The DAS for DEComni Software Returned Values and Associated Error Messages Index Examples 3-1 Connecting To an MMS/SINEC-AP/SINEC-H1 Device.................................... 3-3 3-2 Disconnecting an MMS/SINEC-AP/SINEC-H1 Device.................................... 3-3 3-3 Read Data Screen.......................... 3-8 3-4 Read Data Screen with Data Array.......... 3-8 3-5 Write Data Screen......................... 3-9 3-6 Write Data Screen with Data Array......... 3-9 3-7 Read message procedure.................... 3-10 3-8 Write message procedure................... 3-12 3-9 Directory Screen.......................... 3-16 3-10 Upload and Download Screen................ 3-16 Figures 1-1 DAS for DEComni Software Structure........ 1-2 3-1 Program Invocations State Table........... 3-18 3-2 Read Status Screen........................ 3-19 3-3 Unsolicited Point Definition.............. 3-26 3-4 Scattered Pollset Definition.............. 3-28 v Tables 1-1 MMS Client Supported Services............. 1-4 1-2 Proposed MMS Conformance Building Blocks.................................... 1-5 1-3 SINEC-AP and SINEC-H1 Client Supported Services.................................. 1-6 1-4 Proposed SINEC-AP and SINEC-H1 Conformance Building Blocks........................... 1-7 2-1 Disk Space Requirements................... 2-3 2-2 Files created during installation......... 2-10 2-3 BASEstar Classic Parameters............... 2-15 2-4 CREATE TYPE............................... 2-17 2-5 CREATE PATH............................... 2-18 2-6 CREATE DEVICE............................. 2-19 2-7 Application Simple Name attributes........ 2-21 3-1 DAS for DEComni Software Supported Data Addressing................................ 3-4 3-2 DAS for DEComni Software Supported Data Types..................................... 3-6 3-3 DAS for DEComni Software Supported Address Postfix Values............................ 3-7 3-4 ILAN$DEVICE_SPECIFIC Function Codes....... 3-10 3-5 Logical Status Meaning.................... 3-20 3-6 Physical Status Meaning................... 3-20 3-7 Unsolicited ID Values..................... 3-25 vi _________________________________________________________________ Preface This document describes how to install and use the BASEstar Classic DAS for DEComni software. Intended Audience This document is intended for use by system managers who must set up and maintain the following: o BASEstar Classic for OpenVMS software o BASEstar Classic DAS for DEComni software This document is also intended for use by application programmers who develop shop-floor management software layered on BASEstar Classic for OpenVMS. 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 DEComni devices 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 DEComni software. o Chapter 2 provides information you need to install the DAS for DEComni software. o Chapter 3 provides information about the supported functions for DEComni devices, and how to access those functions. vi Associated Documents Further information on topics covered in this document can be found in the following documents: For information on BASEstar Classic see the following documnents: o BASEstar Classic System Management Documentation, VOLUME 1: - BASEstar Classic Release Notes - BASEstar Classic Installation Guide - BASEstar Classic Configuration and Tuning Guide o BASEstar Classic General User Documentation, VOLUME 2: - BASEstar Classic Introduction - BASEstar Classic Menu Interface User's Guide - BASEstar Classic Command Line Interface User's Guide o BASEstar Classic Programming Documentation, VOLUME 3: - BASEstar Classic Introduction to Callable Services - BASEstar Classic Guide to Writing a Database Server - BASEstar Classic Guide to Writing Device Access Software - BASEstar Classic DEC Rdb Database Server Guide - BASEstar Classic Device Access Software Guide o BASEstar Classic Programming Documentation, VOLUME 4: - BASEstar Classic Application Programming Interface Reference Guide For information MMS ISO/IEC 9506 see the following documents: o Industrial automation systems - Manufacturing Message Specification - Part 1: Service definition - Part 1: Service definition vii For information on DEComni software see the following documents: o DEComni for OpenVMS Installation Guide o DEComni Omni Definition Facility User's Guide o DEComni Application Interface User's Guide For information on DECosap software see the following documents: - DECosap/VMS Installation Guide - DECosap/VMS Network Manager's Guide For information on DECnet/OSI see the following documentS: o DECnet/OSI for OpenVMS Installation and Configuration o DECnet/OSI for OpenVMS Introduction and Planning o DECnet/OSI for OpenVMS Network Management o DECnet/OSI for OpenVMS Network Control Language Reference o DECnet/OSI for OpenVMS Common Trace Facility Use Conventions This manual 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 . viii 1 _________________________________________________________________ Overview of DAS for DEComni Software This chapter provides an overview of the DAS for DEComni software for MMS compliant programmable devices. It also includes a brief description of DEComni device communications, and the supported functions of the DAS for DEComni software. 1.1 Description The DAS for DEComni software allows you to access devices which implement the Manufacturing Message Specifications (MMS), ISO IS-9506 and/or the Siemens SINEC-AP and SINEC- H1 protocol through BASEstar Classic device connection managment. Device connection management is a component of the BASEstar Classic for OpenVMS, which is an engineered family of software components and services that facilitate the development and integration of manufacturing automation solutions. The BASEstar Classic DAS for DEComni software provides an interface between BASEstar Classic and DEComni software, the Digital product which implements MMS application protocol. (Under Version 3.0 and following of DEComni software, the DEComni API and MMS protocol are split into separate products.) Furthermore, the DAS for DEComni software provides an interface between BASEstar Classic and the Siemens SINEC-AP/H1 protocol using DECosap software, the Digital product which implements this protocol under the DEComni software architecture. Using the DAS for DEComni software users or applications can perform a variety of device access functions for devices which implement MMS and/or SINEC-AP/H1 protocols. The DAS for DEComni software receives a request for device access and uses the appropriate sequence of DEComni calls to forward the request to the device. DEComni responds to the request and sends the request status back to the DAS. Overview of DAS for DEComni Software 1-1 Overview of DAS for DEComni Software 1.2 Device Communications 1.2 Device Communications The DAS for DEComni software consists of a Protocol Emulator (PE) and a Network Interface (NI). The PE translates the BASEstar Classic DCM's generic services into calls to the DEComni callable interface, making data access transparent to users. The PE also creates and maintains the DEComni data structures. The NI is the communication module. In the DAS for DEComni software, the NI is only responsible for initializing DEComni. For all other definitions, ie. VMDs, Variable Names and Data Types, the DAS for DEComni software only makes usage of the definitions made under BASEstar Classic software. Definitions are not taken from the DEComni ODF object definitions, thus making the DAS for DEComni software totally independent from the DEComni data definitions and thus avoids the need for duplicate data definitions. The DAS for DEComni software must be installed on an OpenVMS system that is connected to the MMS/SINEC-AP /SINEC-H1 device(s) via an 802.3 network. Connections may be made either directly on the same network backbone as the device(s) or indirectly via a bridge, the exact configuration will be dependent on the type of OpenVMS system used, the device network media and the specific networking topology requirements. Figure 1-1 shows how the DAS for DEComni software facilitates communications between device connection management and the devices. Figure 1-1 DAS for DEComni Software Structure 1-2 Overview of DAS for DEComni Software Overview of DAS for DEComni Software 1.3 Supported Functions 1.3 Supported Functions You can perform only the BASEstar Classic functions that are supported by a device's PE. These functions can be accessed through the BASEstar Classic software's menu system, commands, and callable services. 1.3.1 Supported MMS Functions The DAS for DEComni software supports the following BASEstar Classic functions using MMS compliant devices: o Read and Write Named and Unnamed Variables (Client and Server) o Receive Unsolicited Variables (Information Reports, Read and Write Indications) o Read Device Status and Identification o Download and Upload Domains (Programs and Data) o Start and Stop Programs (Program Invocations) o Get Device Directory (Get Name List) Table 1-1 lists MMS client supported services. See the Industrial automation systems - Manufacturing Message Specification Part 1: Service definition for a definition of the MMS services. Overview of DAS for DEComni Software 1-3 Overview of DAS for DEComni Software 1.3 Supported Functions Table_1-1_MMS_Client_Supported_Services____________________ MMS_Service_______________BASEstar_Classic_DCM_Function____ Identify Read Status Status Read Status GetCapabilityList Read Status ReadVariable Read Data WriteVariable Write Data InformationReport Unsolicited Data Management GetNameList Directory InitiateDownloadSequence Download DownloadSegment Download TerminateDownloadSequence Download InitiateUploadSequence Upload UploadSegment Upload TerminateUploadSequence Upload CreateProgramInvocation Start Program DeleteProgramInvocation Stop Program Start Start Program Stop Stop Program Reset Stop Program UnsolicitedStatus Log Service Initiate Enable Device Conclude Disable Device Abort_____________________Disable_Device___________________ Table 1-2 lists the MMS conformance building blocks. See the Industrial automation systems - Manufacturing Message Specification Part 1: Service definition for information on conformance building blocks. 1-4 Overview of DAS for DEComni Software Overview of DAS for DEComni Software 1.3 Supported Functions Table_1-2_Proposed_MMS_Conformance_Building_Blocks_________ Proposed_CBBs______________________________________________ STR1 Y STR2 Y NEST 10 VNAM Y VADR Y Max Segment Size 512 Version___________________0/1______________________________ The maximum segment size can be specified by setting the IOSIZE parameter in the path definition. 1.3.2 Supported SINEC-AP and SINEC-H1 Functions The DAS for DEComni software supports the following BASEstar Classic functions using SINEC-AP and SINEC-H1 compliant devices: o Read and Write Named and Unnamed Variables (Client and Server) o Receive Unsolicited Variables (Information Reports, Read and Write Indications) o Read Device Status and Identification o Download and Upload Domains (Programs and Data) o Start and Stop Programs (Program Invocations) o Get Device Directory (Get Name List) o Read, Write and Exchange SINEC-AP and SINEC-H1 Messages (Client and Server) Table Table 1-3 lists SINEC-AP and SINEC-H1 client supported services. See the Industrial automation systems - Manufacturing Message Specification Part 1: Service definition for a definition of the MMS services. Overview of DAS for DEComni Software 1-5 Overview of DAS for DEComni Software 1.3 Supported Functions Table_1-3_SINEC-AP_and_SINEC-H1_Client_Supported_Services__ SINEC-AP and SINEC-H1 Service___________________BASEstar_Classic_DCM_Service_____ Identify Read Status Status Read Status GetCapabilityList Read Status ReadVariable Read Data WriteVariable Write Data InformationReport Unsolicited Device Connect Management GetNameList Directory InitiateDownloadSequence Download DownloadSegment Download TerminateDownloadSequence Download InitiateUploadSequence Upload UploadSegment Upload TerminateUploadSequence Upload CreateProgramInvocation Start Program DeleteProgramInvocation Stop Program Start Start Program Stop Stop Program Reset Stop Program UnsolicitedStatus Log Service Initiate Enable Device Conclude Disable Device Abort_____________________Disable_Device___________________ Table 1-4 lists the SINEC-AP and SINEC-H1 conformance building blocks. See the Industrial automation systems - Manufacturing Message Specification Part 1: Service definition for information on conformance building blocks. 1-6 Overview of DAS for DEComni Software Overview of DAS for DEComni Software 1.3 Supported Functions Table 1-4 Proposed SINEC-AP and SINEC-H1 Conformance __________Building_Blocks__________________________________ Proposed_CBBs______________________________________________ STR1 Y STR2 Y NEST 10 VNAM Y VADR Y Max_Segment_Size__________4096_____________________________ The maximum segment size can be specified by setting the IO_SIZE parameter in the path definition. 1.4 Non-supported Functions The MMS specification provides a rich variety of device /application functions of which only a sub-set are typically supported by MMS/AP devices, typically MAP Classes 2 or 3. The DAS for DEComni software can act as a MMS Server for a subset of MMS functions, ie. read, write and status. For detailed information about the supported functions, see Chapter 3. Overview of DAS for DEComni Software 1-7 2 _________________________________________________________________ Installing the DAS for DEComni Software This chapter provides the information you need to install the DAS for DEComni software 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 DEComni software 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 DAS for DEComni software communicates to MMS devices over a full ISO/OSI seven layer stack using an 802.3 Ethernet Bus network. SINEC-AP/H1 devices communications uses the first four layers of the ISO/OSI stack over an 802.3 Ethernet network. You will require the appropriate OpenVMS communications network interface and/or bridges to connect the OpenVMS system and MMS/SINEC-AP/SINEC-H1 devices together. The same OpenVMS 802.3 Ethernet interface may be used for both DECnet and MMS/SINEC-AP/SINEC-H1 communications. The hardware requirements for the DAS for DEComni software are the same as those for BASEstar Classic. For specific hardware requirements, see the BASEstar Classic Installation Guide. Installing the DAS for DEComni Software 2-1 Installing the DAS for DEComni Software 2.1 Installation Requirements 2.1.2 Software Requirements Before installing the DAS for DEComni software, the following software must already be installed: [2] o OpenVMS Version 5.5-2 or higher (VAX) o OpenVMS Version 6.1 or higher (Alpha) o DECnet/OSI Version 5.6B or higher (VAX)[1] o DECnet/OSI Version 5.7 or higher (Alpha)[1] o OSI Session Application Kernel (OSAK) Version 3.0 o DEComni for OpenVMS Version 2.0A or higher (VAX) o DEComni for OpenVMS Version 2.1 or higher (Alpha) o BASEstar Classic for OpenVMS, Version 3.4 or higher If BASEstar Classic for OpenVMS is not already installed on your system, see 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 Additional Software Requirements In order to support the Siemens SINEC-AP and SINEC-H1 functions, the following software must also be installed: [2] o DECosap/VMS Version 2.0B or higher[2] ____________________ [2] Refer to the DECnet/OSI for OpenVMS Installation and Configuration to determine the minimum version of DECnet/OSI required for the version of OpenVMS software installed. [2] Refer to the DECosap/VMS Installation Guide to determine the minimum version of DEComni or DEComni- API required for the version of DECosap software installed. 2-2 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.1 Installation Requirements If using DEComni software version 3.0 or later, the following software must also be installed to support MMS functions: o DEComni-MMS Version 3.0 or higher 2.1.4 Disk Space Requirements Table 2-1 lists the disk space required to install the DAS for DEComni software. The space requirements are approximations; actual sizes may vary depending on your system environment, configuration, and software options installed. Table_2-1_Disk_Space_Requirements__________________________ Usage_____________________Approximate_Space_Requirements___ Peak (during 1000 blocks (VAX) installation) 2250 blocks (Alpha) Net (after installation) 650 blocks (VAX) ________________________________1100_blocks_(Alpha)________ Installing the DAS for DEComni Software 2-3 Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software When your system meets all the hardware and software requirements, you can install the DAS for DEComni software. The installation takes from 5 to 10 minutes, depending on system load and configuration. Install the DAS for DEComni software 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_OMNIVV034 DDCU: where: o DCM_OMNIVV034 argument is the kit name o 034 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 VMSINSTAL prompts you for information during the installation. The following is an example of the output from the installation. OpenVMS VAX Software Product Installation Procedure V6.1 It is 14-OCT-1996 at 13:43. 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_OMNIVV V3.4 Beginning installation of DCM_OMNIVV V3.4 at 13:43 2-4 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software %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 1990, 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 DEComni Software installation procedure. Checking for a valid license... Product: DAS-OMNI-CL Producer: DEC Version: 3.4 Release Date: 13-DEC-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 that DEComni Software is installed... 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]? The installation procedure has no further questions to ask and will complete in 2 to 10 minutes depending on the system and system load. ------------------------------------------------------------------------------ The configuration template file for DEComni support, DCM_OMNI_CONFIG.TEMPLATE, is used to define the DEComni paths, types, and devices. Edit this file, as necessary, to reflect your specific site configuration. Installing the DAS for DEComni Software 2-5 Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software During installation it will be placed in the directory BCC$SYSDATA. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ The startup file for ILAN$DEVSRV, ILAN$SYSTEM_STARTUP.COM must be modified in order to use the DAS for DEComni Software. This installation provides a substitute template for this file called ILAN$SYSTEM_STARTUP.TEMPLATE with modified privileges and quotas. After installation, edit this file as necessary to match your site requirements. Be sure to restore this edited file when upgrading BASEstar Classic software to a new version. During installation it will be placed in the directory BCC$SYSDATA. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ A utility to show the configuration of all DEComni devices, DCM_OMNI$SHOW_DEVICE.COM is provided with this DAS. This utility extracts definitions from the BASEstar Classic database as well as from ODS and allows you to see the configuration of all your DEComni devices. During installation it will be placed in the directory BCC$SYSTEM. ------------------------------------------------------------------------------ Now linking ILAN_OMNI shared image... Now linking IVP test routines... %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.DCM_OMNI]. %CREATE-I-EXISTS, VMI$COMMON:[SYSTEST.DCM_OMNI] already exists %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Copyright (C) Digital Equipment Corporation 1990, 1996. All rights reserved. Executing the Installation Verification Procedure. Now checking OSI version... DECnet OSI V6.3 is supported. Now checking process privileges... Now checking that files have reached target directories... 2-6 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software The next part of the IVP tests DAS connections. To test DAS connections test paths, types and devices are created and communications are simulated using a test program. * OK to continue IVP? [YES] Creating objects for MMS runtime test... Creating MMS OSI transport template... Processing NSAP 49::00-22:AA-00-04-00-73-89:20 (LOCAL:.OHF.BASEY) Creating MMS ODS definitions... Creating MMS BASEstar Classic objects... BASEstar V3.4 for VMS Copyright (c) 1994, Digital Equipment Corporation. All Rights Reserved. %BCC-S-OBJCRE, DCM_OMNI$MMS_TYP created. %BCC-S-OBJCRE, DCM_OMNI$MMS_PTH created. %BCC-S-OBJCRE, DCM_OMNI$MMS_IVP created. Now running the MMS-IS receiver application... IVP_MMS_RCVR: Starting the IVP receiver. IVP_MMS_RCVR: listening... Now trying to access an MMS device. Now writing to the MMS device. IVP_MMS_RCVR: Accepted the connect. Device : DCM_OMNI$MMS_IVP Address : var_1 Format : S_LONGWORD IVP_MMS_RCVR: Received a write variable request... Now reading from the MMS device. IVP_MMS_RCVR: Received a read variable request... Device : DCM_OMNI$MMS_IVP Address : var_1 Format : S_LONGWORD Installing the DAS for DEComni Software 2-7 Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software Data: 0 : 10 IVP_MMS_RCVR: received an ABORT. IVP_MMS_RCVR: All done... Creating objects for SINEC-AP runtime test... Creating SINEC-AP OSI transport template... Routing inactive area defined = {49::FF-00} Local SINEC-AP/H1 address = AA0004007389 Creating SINEC-AP ODS definitions... Creating SINEC-AP BASEstar Classic objects... BASEstar V3.4 for VMS Copyright (c) 1994, Digital Equipment Corporation. All Rights Reserved. %BCC-S-OBJCRE, DCM_OMNI$AP_TYP created. %BCC-S-OBJCRE, DCM_OMNI$AP_PTH created. %BCC-S-OBJCRE, DCM_OMNI$AP_IVP created. Now running the SINEC-AP receiver application... IVP_AP_RCVR: Starting the IVP receiver. IVP_AP_RCVR: listening... Now trying to access a SINEC-AP device. Now writing to the SINEC-AP device. IVP_AP_RCVR: Accepted the connect. Device : DCM_OMNI$AP_IVP Address : var_1 Format : S_LONGWORD IVP_AP_RCVR: Received a write variable request... Now reading from the SINEC-AP device. IVP_AP_RCVR: Received a read variable request... Device : DCM_OMNI$AP_IVP Address : var_1 Format : S_LONGWORD 2-8 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software Data: 0 : 10 IVP_AP_RCVR: received an ABORT. IVP_AP_RCVR: All done... Creating objects for SINEC-H1 runtime test... Creating SINEC-H1 OSI transport template... Routing inactive area defined = {49::FF-00} Local SINEC-AP/H1 address = AA0004007389 Creating SINEC-H1 ODS definitions... Creating SINEC-H1 BASEstar Classic objects... BASEstar V3.4 for VMS Copyright (c) 1994, Digital Equipment Corporation. All Rights Reserved. %BCC-S-OBJCRE, DCM_OMNI$H1_TYP created. %BCC-S-OBJCRE, DCM_OMNI$H1_PTH created. %BCC-S-OBJCRE, DCM_OMNI$H1_IVP created. Now running the SINEC-H1 receiver application... IVP_H1_RCVR: Starting the IVP receiver. IVP_H1_RCVR: listening... Now trying to access a SINEC-H1 device. IVP_H1_RCVR: Accepted the connect. Now writing to the SINEC-H1 device. Device : DCM_OMNI$H1_IVP Address : U\DB:190:7 Format : S_LONGWORD IVP_H1_RCVR: Received a write variable request... Now reading from the SINEC-H1 device. IVP_H1_RCVR: Received a read variable request... Device : DCM_OMNI$H1_IVP Address : U\DB:190:7 Format : S_LONGWORD Installing the DAS for DEComni Software 2-9 Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software Data: 0 : 10 IVP_H1_RCVR: received an ABORT. IVP_H1_RCVR: All done... The BASEstar Classic DAS for DEComni Software IVP has successfully completed. Installation of DCM_OMNIVV V3.4 completed at 13:46 VMSINSTAL procedure done at 13:46 2.2.1 Files Created During Installation Table 2-2 lists the files created by the DAS for DEComni software installation procedure, and the directories in which those files are placed. Table_2-2_Files_created_during_installation________________ Directory________Filename__________________________________ BCC$SYSDATA: ILAN$SYSTEM_STARTUP.TEMPLATE DCM_OMNI_CONFIG.TEMPLATE BCC$SYSTEM: DCM_OMNI$SHOW_DEVICE.COM SYS$LIBRARY: ILAN_OMNI.EXE SYS$HELP: DCM_OMNIVV034.RELEASE_NOTES (VAX) DCM_OMNIVA034.RELEASE_NOTES (Alpha) SYS$TEST: DCM_OMNI$IVP.COM SYS$COMMON: DCM_OMNI$IVP_MMS_RCVR.EXE [SYSTEST.DCM_ DCM_OMNI$IVP_AP_RCVR.EXE OMNI] DCM_OMNI$IVP_H1_RCVR.EXE _________________DCM_OMNI$STOP_DCM.EXE_____________________ 2-10 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software 2.2.2 Installation Messages You may see VMSINSTAL messages during the installation procedure. BADBCC, BASEstar Classic software must be installed before the DAS for DEComni Software. 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 DEComni Software. 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. BADDECOMNI (VAX), The DAS for DEComni Software must be installed under DEComni 2.0A or greater. Explanation: Error. An incorrect version of DEComni for OpenVMS was installed on this system. User Action: Install DEComni for OpenVMS V2.0A or higher and then reinstall the DAS for DEComni software. BADDECOMNI (Alpha), The DAS for DEComni Software must be installed under DEComni 2.1 or greater. Explanation: Error. An incorrect version of DEComni for OpenVMS was installed on this system. User Action: Install DEComni for OpenVMS V2.1 or higher and then reinstall the DAS for DEComni software. BADVMS (VAX), The DAS for DEComni Software 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 DEComni Software must be installed under OpenVMS V6.1 or greater. Explanation: Error. Incorrect version of OpenVMS. User Action: Install OpenVMS V5.5-2 or higher. Installing the DAS for DEComni Software 2-11 Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software BCCNORUN, BASEstar Classic will be started, please wait. Explanation: Informational. The installation procedure is starting BASEstar Classic. User Action: None. BCCSTART, Starting BASEstar Classic, please wait ... Explanation: Informational. The installation procedure has started BASEstar Classic and is waiting for the status to go to "running". User Action: None. BSTARRUN, BASEstar Classic is now running. Explanation: Informational. The installation procedure has completed starting BASEstar Classic. User Action: None. NETBLOCKS (VAX), The BASEstar Classic DAS for DEComni V3.4 requires 650 blocks after installation. Explanation: Error. Not enough disk space to complete installation. User Action: Delete any unnecessary files, then reinstall. NETBLOCKS (Alpha), The BASEstar Classic DAS for DEComni V3.4 requires 1100 blocks after installation. Explanation: Error. Not enough disk space to complete installation. User Action: Delete any unnecessary files, then reinstall. NODECOMNI, Your system does not have DEComni for OpenVMS installed Explanation: Error. DEComni for OpenVMS must be installed before the DAS for DEComni Software. User Action: Install DEComni for OpenVMS and then install the DAS for DEComni software. 2-12 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.2 Installing the BASEstar Classic DAS for DEComni Software NORDB, You have Multi-version RDB but the current RDB version is not set, please issue @SYS$LIBRARY:RDBVMS_SETVER.COM and repeat the DAS for DEComni Software installation. Explanation: Error. Don't know which SQL library to link against. User Action: Execute @SYS$LIBRARY:RDBVMS_SETVER.COM and repeat the DAS for DEComni Software installation. 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. 2.3 Post Installation Tasks This section describes the tasks to perform after installing the DAS for DEComni software, including editing the configuration file, setting the BASEstar Classic support block parameter, and setting up shop floor equipment. 2.3.1 Configuring layered products See the related DEComni/DECosap and DECnet/OSI documentation for configuring the layered products used by the DAS for DEComni software. Installing the DAS for DEComni Software 2-13 Installing the DAS for DEComni Software 2.3 Post Installation Tasks 2.3.2 Tuning ILAN$DEVSRV The installation procedure provides a replacement for the ILAN startup file, ILAN$SYSTEM_STARTUP.TEMPLATE. The new file has been provided because the ILAN$DEVSRV image using the DAS for DEComni software needs additional quotas and privileges. The values used in the provided startup file are valid for a typical configuration and may be more or less than is actually required for your installation. ________________________ Note ________________________ If quotas are not set properly, it is likely that the ILAN$DEVSRV process will ACCVIO or otherwise fail with very little diagnostic information provided. If you find that the ILAN$DEVSRV process is ACCVIOing soon after enabling devices or soon after startup, monitor the process using SHOW PROCESS/QUOTA/ID=XXXXXXXX to determine which quota the process is running low on. ______________________________________________________ SYSGEN parameters may also need adjusting. Parameters which may need modifying include the following: - CHANNELCNT - VIRTUALPAGECNT BASEstar Classic parameters may also need adjusting, depending on the number of devices configured. Parameters which may need modifying include the following: - ILAN$MAX_DEVICES - ILAN$MAX_OUT_REQUESTS - ILAN$MAX_SPT_REQUESTS - ILAN$MAX_DSEC_SIZE See BASEstar Classic Configuration and Tuning Guide for details on changing BASEstar Classic parameters. 2-14 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks 2.3.3 Defining DEComni Constants A BASEstar Classic parameter is used to configure the maximum number of OMNI devices that can be created. This parameter is created as part of the DAS installation. To change the value of this parameter, change the value using the BASEstar Classic CLI. Then stop and restart BASEstar Classic to to enable the DAS to use the new parameter value. Table 2-3 lists the default and maximum value for this parameter. Table_2-3_BASEstar_Classic_Parameters______________________ Default Parameter__________________Value_______Max_Value___________ ILAN$OMNI_MAX_DEVICES_________64__________500______________ 2.3.4 Editing the Configuration File A configuration file is supplied with the DAS for DEComni software. The configuration file contains definitions for types, paths, and devices. o Type record-represents a Protocol Emulator (PE) o Path record-represents a Network Interface (NI) o Device record-represent a device. The following sections give examples of the type, path, and device records. See the BASEstar Classic Command Line Interface User's Guide for more information about creating type, path, and device definitions. 2.3.4.1 Editing Type Records The following example shows the type records created by the configuration file. create type MMS_IS_TYPE/manufacturer=DEC/model="MMS-IS\MMS-IS device"- /protocol=OMNI - /description="MMS-IS ISO 9506 compliant device"/log create type MMS_DIS_TYPE/manufacturer=DEC/model="MMS-DIS\MMS-DIS device"- /protocol=OMNI - /description="MMS-DIS ISO 9506 compliant device"/log Installing the DAS for DEComni Software 2-15 Installing the DAS for DEComni Software 2.3 Post Installation Tasks create type AP_TYPE/manufacturer="Siemens-AG"/model="AP\DECosap device"- /protocol=OMNI - /description="Siemens SINEC-AP device"/log create type H1_S115U_941_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-941"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S115U_942_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-942"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S115U_943_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-943"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S115U_944_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-944"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S135U_921_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_135U-921"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S135U_922_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_135U-922"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S135U_928_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_135U-928"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S150U_TYPE/manufacturer="Siemens-AG"- /model="H1\SIMATIC_150U"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S155U_TYPE/manufacturer="Siemens-AG"- /model="H1\SIMATIC_155U"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log 2-16 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks Table 2-4 lists the types and parameters of the CREATE TYPE command, and indicates the parameters of the previous example that you can change. Table_2-4_CREATE_TYPE______________________________________ Parameter_________Modifiable?______________________________ Manufacturer Yes Model Yes[1] Protocol No Description Yes [1]The_text_before_the_\_is_not_modifiable._The_text_after_ the \ is used in defining the model to DEComni. For SINEC- H1 devices, the model field is not modifiable. ___________________________________________________________ The model is used to define the protocol profile used by the DAS in defining the device to DEComni. The DAS for DEComni software currently supports MMS-IS, MMS-DIS, AP and H1 protocols. 2.3.4.2 Editing Path Records The following example shows the path records included in the configuration file. The commands are commented out in the configuration file so edit the commands and then remove the comment character before executing the configuration file. create path MMS_IS_LCL_PATH/vaxport="MMS_IS_LOCAL_PLC"/netname=OMNI- /multidrop/io_size=512/log create path MMS_DIS_LCL_PATH/vaxport="MMS_DIS_LOCAL_PLC"/netname=OMNI- /multidrop/io_size=512/log create path AP_LOCAL_PATH/vaxport="S5_AP_LOCAL_PLC"/netname=OMNI- /multidrop/io_size=4096/log create path H1_LOCAL_PATH/vaxport="S5_H1_LOCAL_PLC"/netname=OMNI- /multidrop/io_size=4096/log Installing the DAS for DEComni Software 2-17 Installing the DAS for DEComni Software 2.3 Post Installation Tasks The VAXPORT field contains the local Application Simple Name. This application simple name must be defined in ODS (OMNI Directory Services) to define the network address information for the local VMD. Only one path is required to be defined for each protocol profile. However, multiple paths may be defined if it is desired to define a unique local VMD for each remote VMD. See the discussion in Section 3.3 for more information on defining multiple local paths. Table 2-5 lists the paths and parameters of the CREATE PATH command, and indicates the parameters that you can change. Table_2-5_CREATE_PATH______________________________________ Parameter_________Modifiable?______________________________ Vaxport[1] Yes Netname No Multidrop No IO size Yes[2] Retries Yes[3] Line Yes[3] [1]Specifies_a_local_Application_Simple_Name._Application__ Simple Names must be unique. [2]Specifies the maximum segment value used in defining the device to DEComni. [3]These values are not used by the DAS. ___________________________________________________________ 2.3.4.3 Editing Device Records The following example shows the device records created by the configuration file. NOTE: The device MUST be defined with the UNSOLICITED attribute. create dev MMS_IS_PLC_NO_01/path=MMS_IS_LCL_PATH/type=MMS_IS_TYPE- /netaddr=MMS_IS_PLC_NO_01/unsol/timeout=600/log create dev MMS_DIS_PLC_NO_01/path=MMS_DIS_LCL_PATH/type=MMS_DIS_TYPE- /netaddr=MMS_DIS_PLC_NO_01/unsol/timeout=600/log create dev S5_AP_PLC_NO_01/path=AP_LOCAL_PATH/type=AP_TYPE- /netaddr=S5_AP_PLC_NO_01/unsol/timeout=600/log 2-18 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks create dev S5_H1_PLC_NO_01/path=H1_LOCAL_PATH/type=H1_S150U_TYPE- /netaddr=S5_H1_PLC_NO_01/unsol/timeout=600/log The device name is the name of a remote VMD. Remote VMD names and related definitions (variables, domains, etc.) need not be defined in the DEComni database. They are created at run-time by the DAS for DEComni software and are taken from the BASEstar Classic definitions ONLY. 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____________________________________ Parameter___Modifiable?____________________________________ Path Yes Type No Description Yes Timeout Yes Netaddr[1] Yes Unsolicited No [1]Specifies_a_remote_Application_Simple_Name._Application_ Simple Names must be unique. ___________________________________________________________ ________________________ NOTE ________________________ The device definition MUST be defined as UNSOLICITED. Failure to do so will prevent the DAS for DEComni software from being able to react to Abort or Conclude indications sent either by the target device or the local OSI network. ie. the DAS for DEComni software will be unaware that its connection with the remote device has been terminated. Recovery will require that the user disable and re-enable the device after which a connection will be re-established. Furthermore, failure to specify support for Unsolicited data means that the DAS for DEComni software will buffer all unsolicited data from the device. This will eventually Installing the DAS for DEComni Software 2-19 Installing the DAS for DEComni Software 2.3 Post Installation Tasks lead to utilization of all the available OpenVMS virtual memory. Subsequently the DAS for DEComni software and ILAN will be unable to continue and will automatically shut themselves down. ______________________________________________________ The local and remote Application Simple Names must be configured with ODSCL. The following examples shows the ODSCL commands contained in the configuration file. $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=MMS_IS_LOCAL_PLC" REGISTER DIRECTORY NAME "/CN=MMS_IS_LOCAL_PLC"- ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 2 3}- /P_ADDR=0x01.0x01.0x01.INTERNET%49003FAA00040013FD21" EXIT $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=MMS_IS_PLC_NO_01" REGISTER DIRECTORY NAME "/CN=MMS_IS_PLC_NO_01"- ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 2 3}- /P_ADDR=0x02.0x02.0x02.INTERNET%49003FAA00040013FD21" EXIT $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=MMS_DIS_LOCAL_PLC" REGISTER DIRECTORY NAME "/CN=MMS_DIS_LOCAL_PLC"- ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 1 1}- /P_ADDR=0x01.0x01.0x01.INTERNET%49003FAA00040013FD21" EXIT $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=MMS_DIS_PLC_NO_01" REGISTER DIRECTORY NAME "/CN=MMS_DIS_PLC_NO_01"- ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 1 1}- /P_ADDR=0x02.0x02.0x02.INTERNET%49003FAA00040013FD21" EXIT $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=S5_AP_LOCAL_PLC" REGISTER DIRECTORY NAME "/CN=S5_AP_LOCAL_PLC"- ATTRIBUTE "/OC=OSAP/TSAP=OSAPHOST- /NETADDRESS=IEEE%AA00040013FD" EXIT 2-20 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=S5_AP_PLC_NO_01" REGISTER DIRECTORY NAME "/CN=S5_AP_PLC_NO_01"- ATTRIBUTE "/OC=OSAP/TSAP=OSAPTSAP- /NETADDRESS=IEEE%AA00040013FD" EXIT $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=S5_H1_LOCAL_PLC" REGISTER DIRECTORY NAME "/CN=S5_H1_LOCAL_PLC"- ATTRIBUTE "/OC=OSH1/TSAP=OSH1HOST- /NETADDRESS=IEEE%AA00040013FD" EXIT $ RUN ODS:[EXE]ODSCL DEREGISTER DIRECTORY NAME "/CN=S5_H1_PLC_NO_01" REGISTER DIRECTORY NAME "/CN=S5_H1_PLC_NO_01"- ATTRIBUTE "/OC=OSH1/TSAP=OSH1TSAP- /NETADDRESS=IEEE%AA00040013FD" EXIT Table 2-7 lists the attributes for ODS Application Simple Names for MMS-IS, MMS-DIS, SINEC-AP and SINEC-H1 Application Profiles. Table_2-7_Application_Simple_Name_attributes_____________________ Application Profile_____Attribute________Description________________Modifiable? MMS-IS OC[1] Object Class No CN[2] Common Name Yes APT[3][4] Application Process Title Yes [1]OC=TAE_(Titled_Application_Entity)____________________________ [2]The common name entry must equal the name specified in the corresponding VAXport definition. [3]The APT, AEQ and P_ADDR must be unique for a given node. APT and AEQ are optional attributes. If APT and AEQ are not specified, then DEComni uses the P_ADDR only in matching incoming initiate requests. [4]See the vendor documentation for the remote VMD to see how this item is defined in the remote VMD. (continued on next page) Installing the DAS for DEComni Software 2-21 Installing the DAS for DEComni Software 2.3 Post Installation Tasks Table_2-7_(Cont.)_Application_Simple_Name_attributes_____________ Application Profile_____Attribute________Description________________Modifiable? AEQ[3][4] Application Entity Yes Qualifier APC[5] Application Context No P_ADDR[6][4] Presentation Address Yes MMS-DIS OC[1] Object Class No CN[2] Common Name Yes APT[3][4] Application Process Title Yes AEQ[3][4] Application Entity Yes Qualifier APC[7] Application Context No P_ADDR[6][4] Presentation Address Yes Sinec AP OC[8] Object Class No CN[2] Common Name Yes TSAP[4] Transport Service Access Yes Point NETADDRESS[9] Network Address Yes RESPTIMER[10] Response timeout Yes COMPLTIMER[10] Completion timeout Yes [1]OC=TAE_(Titled_Application_Entity)____________________________ [2]The common name entry must equal the name specified in the corresponding VAXport definition. [3]The APT, AEQ and P_ADDR must be unique for a given node. APT and AEQ are optional attributes. If APT and AEQ are not specified, then DEComni uses the P_ADDR only in matching incoming initiate requests. [4]See the vendor documentation for the remote VMD to see how this item is defined in the remote VMD. [5]APC={1 0 9506 2 3} [6]The presentation address consists of the PSAP,SSAP,TSAP & NSAP. The NSAP consists of the OSI transport template and the OSI network address of the remote VMD. [7]APC={1 0 9506 1 1} [8]OC=OSAP [9]The network address consists of the null internet OSI template and the ethernet address of the remote VMD. [10]Optional parameter. See DECosap documentation for details. (continued on next page) 2-22 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks Table_2-7_(Cont.)_Application_Simple_Name_attributes_____________ Application Profile_____Attribute________Description________________Modifiable? MUX[10] Yes NEGOTIATION[10] Yes Sinec H1 OC[11] Object Class No CN[2] Common Name Yes TSAP[12] Transport Service Access Yes Point NETADDRESS[9] Network Address Yes RESPTIMER[10] Response Timeout Yes COMPLTIMER[10] Completion Timeout Yes [2]The_common_name_entry_must_equal_the_name_specified_in_the____ corresponding VAXport definition. [9]The network address consists of the null internet OSI template and the ethernet address of the remote VMD. [10]Optional parameter. See DECosap documentation for details. [11]OC=OSH1 [12]The TSAPs in the remote VMD should equal xxxxxxxR, xxxxxxxW, xxxxxxxM for read, write and message access points. _________________________________________________________________ Make sure that the ODSCL attributes match your shop-floor configuration. 2.3.4.4 The DAS for DEComni Software Configuration File Example The following is an example of the DAS for DEComni software configuration file. Installing the DAS for DEComni Software 2-23 Installing the DAS for DEComni Software 2.3 Post Installation Tasks $! $! OMNI support for DCM Device Access. $! $!********************************************************************! $! ! $! This is a template for the OMNI site specific configuration ! $! command file. ! $! Rename and edit this command procedure template to reflect your ! $! site specific OMNI configuration. ! $! You must manually execute this command procedure to configure ! $! your devices. ! $! ! $! Add comments to the site specific changes here. ! $! ! $!********************************************************************! $! $ bstar/dcm !*********************************************************************! ! ! ! Create types for the application profiles supported by the OMNI ! ! PE: DEComni and DECosap. ! ! In general, the type definitions are DAS specific, and should ! ! not be modified. ! ! ! !*********************************************************************! create type MMS_IS_TYPE/manufacturer=DEC/model="MMS-IS\MMS-IS device"- /protocol=OMNI - /description="MMS-IS ISO 9506 compliant device"/log create type MMS_DIS_TYPE/manufacturer=DEC/model="MMS-DIS\MMS-DIS device"- /protocol=OMNI - /description="MMS-DIS ISO 9506 compliant device"/log create type AP_TYPE/manufacturer="Siemens-AG"/model="AP\DECosap device"- /protocol=OMNI - /description="Siemens SINEC-AP device"/log create type H1_S115U_941_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-941"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log 2-24 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks create type H1_S115U_942_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-942"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S115U_943_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-943"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S115U_944_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_115U-944"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S135U_921_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_135U-921"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S135U_922_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_135U-922"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S135U_928_TYP/manufacturer="Siemens-AG"- /model="H1\SIMATIC_135U-928"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S150U_TYPE/manufacturer="Siemens-AG"- /model="H1\SIMATIC_150U"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log create type H1_S155U_TYPE/manufacturer="Siemens-AG"- /model="H1\SIMATIC_155U"- /protocol=OMNI - /description="Siemens SINEC-H1 device"/log exit $ ! $ bstar/dcm Installing the DAS for DEComni Software 2-25 Installing the DAS for DEComni Software 2.3 Post Installation Tasks !*********************************************************************! ! ! ! Modify these path and device definitions for your specific ! ! configuration. ! ! ! !*********************************************************************! !***********************************************************************! ! ! ! Create a vaxport MMS_IS_LOCAL_PLC using MMS-IS ! ! ! !***********************************************************************! !create path MMS_IS_LCL_PATH/vaxport="MMS_IS_LOCAL_PLC"/netname=OMNI- !/multidrop/io_size=512/log $ ! $ ! ... Network Address For MMS_IS_LOCAL_PLC Device ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=MMS_IS_LOCAL_PLC" !REGISTER DIRECTORY NAME "/CN=MMS_IS_LOCAL_PLC"- !ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 2 3}- !/P_ADDR=0x01.0x01.0x01.INTERNET%49003FAA00040013FD21" EXIT !***********************************************************************! ! ! ! Create a MMS_IS_PLC_NO_01 device ! ! ! !***********************************************************************! !create dev MMS_IS_PLC_NO_01/path=MMS_IS_LCL_PATH/type=MMS_IS_TYPE- !/netaddr=MMS_IS_PLC_NO_01/unsol/timeout=600/log exit $ ! $ ! ... Network Address For MMS_IS_PLC_NO_01 Device ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=MMS_IS_PLC_NO_01" !REGISTER DIRECTORY NAME "/CN=MMS_IS_PLC_NO_01"- !ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 2 3}- !/P_ADDR=0x02.0x02.0x02.INTERNET%49003FAA00040013FD21" EXIT 2-26 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks $ ! $ bstar/dcm !***********************************************************************! ! ! ! Create a vaxport MMS_DIS_LOCAL_PLC using MMS-DIS ! ! ! !***********************************************************************! !create path MMS_DIS_LCL_PATH/vaxport="MMS_DIS_LOCAL_PLC"/netname=OMNI- !/multidrop/io_size=512/log $ ! $ ! ... Network Address For MMS_DIS_PLC_NO_01 Device ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=MMS_DIS_LOCAL_PLC" !REGISTER DIRECTORY NAME "/CN=MMS_DIS_LOCAL_PLC"- !ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 1 1}- !/P_ADDR=0x01.0x01.0x01.INTERNET%49003FAA00040013FD21" EXIT !***********************************************************************! ! ! ! Create a MMS_DIS_PLC_NO_01 device ! ! ! !***********************************************************************! !create dev MMS_DIS_PLC_NO_01/path=MMS_DIS_LCL_PATH/type=MMS_DIS_TYPE- !/netaddr=MMS_DIS_PLC_NO_01/unsol/timeout=600/log exit $ ! $ ! ... Network Address For MMS_DIS_PLC_NO_01 Device ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=MMS_DIS_PLC_NO_01" !REGISTER DIRECTORY NAME "/CN=MMS_DIS_PLC_NO_01"- !ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 1 1}- !/P_ADDR=0x02.0x02.0x02.INTERNET%49003FAA00040013FD21" EXIT Installing the DAS for DEComni Software 2-27 Installing the DAS for DEComni Software 2.3 Post Installation Tasks $ ! $ ! $ bstar/dcm !***********************************************************************! ! ! ! Create a vaxport S5_AP_LOCAL_PLC using SINEC-AP ! ! ! !***********************************************************************! !create path AP_LOCAL_PATH/vaxport="S5_AP_LOCAL_PLC"/netname=OMNI- !/multidrop/io_size=4096/log $ ! $ ! ... SINEC-AP ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=S5_AP_LOCAL_PLC" !REGISTER DIRECTORY NAME "/CN=S5_AP_LOCAL_PLC"- !ATTRIBUTE "/OC=OSAP/TSAP=OSAPHOST- !/NETADDRESS=IEEE%AA00040013FD" EXIT !***********************************************************************! ! ! ! Create a S5_AP_PLC_NO_01 device ! ! ! !***********************************************************************! !create dev S5_AP_PLC_NO_01/path=AP_LOCAL_PATH/type=AP_TYPE- !/netaddr=S5_AP_PLC_NO_01/unsol/timeout=600/log exit $ ! $ ! ... SINEC-AP ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=S5_AP_PLC_NO_01" !REGISTER DIRECTORY NAME "/CN=S5_AP_PLC_NO_01"- !ATTRIBUTE "/OC=OSAP/TSAP=OSAPTSAP- !/NETADDRESS=IEEE%AA00040013FD" EXIT 2-28 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks $ ! $ bstar/dcm !***********************************************************************! ! ! ! Create a vaxport S5_H1_LOCAL_PLC using SINEC-H1 ! ! ! !***********************************************************************! !create path H1_LOCAL_PATH/vaxport="S5_H1_LOCAL_PLC"/netname=OMNI- !/multidrop/io_size=4096/log $ ! $ ! ... SINEC-H1 ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=S5_H1_LOCAL_PLC" !REGISTER DIRECTORY NAME "/CN=S5_H1_LOCAL_PLC"- !ATTRIBUTE "/OC=OSH1/TSAP=OSH1HOST- !/NETADDRESS=IEEE%AA00040013FD" EXIT !***********************************************************************! ! ! ! Create a S5_H1_PLC_NO_01 device ! ! ! !***********************************************************************! !create dev S5_H1_PLC_NO_01/path=H1_LOCAL_PATH/type=H1_S150U_TYPE- !/netaddr=S5_H1_PLC_NO_01/unsol/timeout=600/log exit $ ! $ ! ... SINEC-H1 ... $ ! $ RUN ODS:[EXE]ODSCL !DEREGISTER DIRECTORY NAME "/CN=S5_H1_PLC_NO_01" !REGISTER DIRECTORY NAME "/CN=S5_H1_PLC_NO_01"- !ATTRIBUTE "/OC=OSH1/TSAP=OSH1TSAP- !/NETADDRESS=IEEE%AA00040013FD" EXIT $ $ exit For more information about maintaining type, path, and device definitions, see the BASEstar Classic Command Line Interface User's Guide. Installing the DAS for DEComni Software 2-29 Installing the DAS for DEComni Software 2.3 Post Installation Tasks 2.3.4.5 NCL Configuration In order to use the DAS for DEComni software OSI transport templates need to be provided for MMS, AP and H1 connections. To configure OSI transport templates use the command procedure @SYS$STARTUP:NET$CONFIGURE.COM. Select Configure Transports from the menu selection and follow the instructions for configuring the templates. For Sinec AP and Sinec H1, a NULL_INTERNET template must be configured. For MMS, an INTERNET template is configured. For details on configuring templates, see the DECnet/OSI for OpenVMS Installation and Configuration. The following is an example of an NCL configuration script showing creation of transport templates for MMS, H1 and AP protocols. CREATE NODE 0 OSI TRANSPORT TEMPLATE OMNINET SET NODE 0 OSI TRANSPORT TEMPLATE OMNINET NETWORK SERVICE CLNS, - CLASSES {4}, - CONS TEMPLATE , - EXPEDITED DATA TRUE, - CHECKSUMS TRUE, - INBOUND TRUE, - LOOPBACK FALSE CREATE NODE 0 OSI TRANSPORT TEMPLATE OSAPNET SET NODE 0 OSI TRANSPORT TEMPLATE OSAPNET NETWORK SERVICE CLNS, - CLASSES {4}, - CONS TEMPLATE , - EXPEDITED DATA TRUE, - CHECKSUMS TRUE, - INBOUND TRUE, - LOOPBACK FALSE SET NODE 0 OSI TRANSPORT TEMPLATE OSAPNET CLNS INACTIVE AREA ADDRESS {49::FF-00} SET NODE 0 ROUTING CIRCUIT CSMACD-0 INACTIVE AREA ADDRESS = {49::FF-00} CREATE NODE 0 OSI TRANSPORT TEMPLATE H1NET SET NODE 0 OSI TRANSPORT TEMPLATE H1NET NETWORK SERVICE CLNS, - CLASSES {4}, - CONS TEMPLATE , - EXPEDITED DATA TRUE, - CHECKSUMS FALSE, - INBOUND TRUE, - LOOPBACK FALSE SET NODE 0 OSI TRANSPORT TEMPLATE H1NET CLNS INACTIVE AREA ADDRESS {49::FF-00} SET NODE 0 ROUTING CIRCUIT CSMACD-0 INACTIVE AREA ADDRESS = {49::FF-00} 2-30 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.3 Post Installation Tasks ENABLE NODE 0 OSI TRANSPORT CREATE NODE 0 SESSION CONTROL TRANSPORT SERVICE OSI PROTOCOL = %X05 In addition it is recommended that you modify the keepalive timer from the default of 60 seconds to a value of 5 seconds in order for the DAS to be notified promptly of a broken connection. Other timers in the transport template may need to be modified depending on your specific hardware and network configuration. To modify transport template values place an NCL script in SYS$COMMON:[SYSMGR] and execute it from your system startup command file. Use the following syntax to execute an NCL script. $RUN SYS$SYSTEM:NCL @SYS$MANAGER:CUSTOM_NCL_SCRIPT.NCL 2.3.5 DAS SPT Block Usage The ILAN$MAX_SPT_REQUESTS parameter specifies the maximum number of blocks allocated in the SPT global section. To set this parameter, perform the following steps: 1. Approximate the SPT blocks for this BASEstar Classic DAS by using the following formula: SPT = 1+num_paths+(6*total_num_devices)+[(3*num_unsol_devices)] where: SPT is the approximate number of blocks for the DAS for DEComni software. num_paths is the number of paths defined in the configuration file. total_num_devices is the total number of DEComni devices defined. num_unsol_devices is the number (if any) of DEComniunsolicted devices defined. Installing the DAS for DEComni Software 2-31 Installing the DAS for DEComni Software 2.3 Post Installation Tasks 2. Use the SPT to calculate the total block requirements for the ILAN$MAX_SPT_REQUESTS parameter. See the BASEstar Classic Configuration and Tuning Guide, for instructions on calculating the total block requirements. 2.3.6 Setting Up Shop Floor Equipment To set up your shop floor equipment, see the documentation for your specific MMS, SINEC-AP or SINEC-H1 compliant device. When configuring MMS devices be sure to note the PSAP, SSAP, TSAP and NSAP. When configuring SINEC-AP or SINEC-H1 devices be sure to note the TSAP. 2.3.7 Tracing OSI Messages The tracing facility enables you to see if, and what actually is send out and received from OpenVMS on the OSI stack. You could invoke the Common Trace Facility for a full and live trace by typing: $ TRACE CTF> START/LIVE/FULL "OSITP CR MESSAGES *" The above trace will trace all connect request protocol data units. See DECnet/OSI for OpenVMS Common Trace Facility Use for a further description of the Common Trace Facility, tracepoints supported and the output generated. 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 2-32 Installing the DAS for DEComni Software Installing the DAS for DEComni Software 2.4 Failures During Product Use 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 version number of DEComni software you are using - The version number of DECosap software you are using (if appropriate) - The version number of DECnet/OSI you are using - The hardware system you are using (such as a model number) - The manufacturer and model numbers of the devices 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. Installing the DAS for DEComni Software 2-33 Installing the DAS for DEComni Software 2.4 Failures During Product Use 5. Mail the SPR package to Digital. 2-34 Installing the DAS for DEComni Software 3 _________________________________________________________________ Using the DAS for DEComni Software This chapter provides information about the supported functions for DEComni devices, and how to access these functions. 3.1 Accessing DEComni Functions The DAS for DEComni software functions are accessed through the BASEstar Classic, using the following interfaces: o Commands o Menu system o Callable services To use the BASEstar Classic services, enter the following command at the DCL prompt ($): $ BSTAR DCM For information about BASEstar Classic commands, see the BASEstar Classic Command Line Interface User's Guide. To use the BASEstar Classic menu system, enter the following command: $ BSTAR/MENU For information about the BASEstar Classic menu system, see the BASEstar Classic Command Line Interface User's Guide. For information about the BASEstar Classic callable services, refer to the BASEstar Classic Application Programming Interface Reference Guide. Using the DAS for DEComni Software 3-1 Using the DAS for DEComni Software 3.2 Supported Functions 3.2 Supported Functions This section describes the functions that are supported by the DAS for DEComni software devices. The DAS for DEComni software supports the following BASEstar Classic functions using MMS compliant devices: o Read and Write Named and Unnamed Variables o Receive Unsolicited Variables (Information Reports, Read and Write Indications) o Receive Unsolicited Status (Status Indication) o Receive Unsolicited Aborts and Concludes (Abort/Conclude Indication) o Read Device Status and Identity o Download and Upload Domains (Programs and Data) o Start and Stop Programs (Program Invocations) o Get Device Directory (Get Name List) The DAS for DEComni software supports the following BASEstar Classic functions using SINEC-AP/H1 compliant devices: o Read and Write Named and Unnamed Variables o Receive Unsolicited Variables (Information Reports, Read and Write Indications) o Receive Unsolicited Status (Status Indication) o Receive Unsolicited Aborts and Concludes (Abort/Conclude Indication) o Read Device Status and Identity o Read, Write and Exchange SINEC-AP and SINEC-H1 Messages 3-2 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions 3.2.1 Connecting To a Device The MODIFY DEVICE/ENABLE command is used to set a device online. The DAS then attempts to connect to the device. If the connection is successful then the connection will remain active until either the device is disabled or an abort/conclude is generated. Should the initial connection request fail, further connection attempts will be made when the devices is requested to perform a function, ie. read status or if the reconnect interval defined for the device has expired. NOTE: The DAS will not accept incoming connection requests from the remote VMD. Example 3-1 shows an example of enabling a device. The first time a device is enabled all the DEComni related data structures have to be built up by the DAS, so this could take a few seconds or more if a lot of variables are defined. Example 3-1 Connecting To an MMS/SINEC-AP/SINEC-H1 Device DCM> modify device TEST_PLC /enable DCM> 3.2.2 Disconnecting a Device The MODIFY DEVICE/DISABLE command is used to set a device offline, Example 3-2 shows an example of this. When a device disabled an abort of the connection is sent to the device. Example 3-2 Disconnecting an MMS/SINEC-AP/SINEC-H1 Device DCM> modify device TEST_PLC /disable DCM> Using the DAS for DEComni Software 3-3 Using the DAS for DEComni Software 3.2 Supported Functions 3.2.3 Read and Write Data Functions Use the BASEstar Classic read data and write data functions to read data from and write data to a specific address in device storage. Address syntax is common for all MMS compliant devices and allows access to both "Named" and "Unnamed" MMS variables. An MMS variable is a typed virtual object that represents an access path to a location on the device ("real" variable). The Named Variable object describes access to the real variable using an application process determined name. It may be used to describe a computed variable or a real variable whose fixed address is not public. The Unnamed Variable object describes access to the real variable using a device-specific address. It requires a known, fixed address for the real variable. Table 3-1 shows the syntax for configuring named and unnamed variable objects. Table 3-1 DAS for DEComni Software Supported Data __________Addressing_______________________________________ BASEstar Classic Data Address_______DEComni_Data_Address_________________________ "XXX" Named variable "XXX" "N\XXX" Named variable "XXX" "U\YYY" Unnamed variable at unconstrained address "YYY" "S\YYY" Unnamed variable at symbolic address "YYY" "X\YYY" Unnamed variable at numeric address "YYY"[1] "M\YYY" Message named "YYY"[2] "MX\YYY" Message named "YYY" - message exchange is performed[2]. "MW\YYY" Message named "YYY" - message send is performed[2]. [1]"YYY"_must_be_a_decimal_number._________________________ [2]"Messages are supported in addresses for SINEC-AP only. ___________________________________________________________ 3-4 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions It is possible to access a variable defined on a domain. To access the named variable "ZZZ" defined on the domain "DDD" the DCM address "DDD.ZZZ" (or "N\DDD.ZZZ") must be used. ________________________ Note ________________________ When defining messages (M\ syntax) the "YYY" portion of the address must always be identical for a particular VMD since DEComni only allows one message to be defined for a particular VMD. Note that the DAS always creates a remote VMD for each device and may also create a local VMD for that device. Message names for the local and remote VMD may be different. ______________________________________________________ ________________________ Note ________________________ The address defined in DCM is used by the DAS as the name of the variable when defining the variable to DEComni. The variable is created in DEComni when the associated device is enabled or, if an ad hoc query is performed, when the request is made. Subsequent variable accesses use the existing variable that was created. For this reason, reading the same variable using different formats will result in erroneous and unpredictable results. Variables created in DEComni cannot be deleted, so a variable remains defined to DEComni until BASEstar Classic is shut down and restarted. ______________________________________________________ Table 3-2 shows Supported data type formats for the DAS for DEComni software. Using the DAS for DEComni Software 3-5 Using the DAS for DEComni Software 3.2 Supported Functions Table_3-2_DAS_for_DEComni_Software_Supported_Data_Types____ DCM_Data_Type____DEComni_Data_Type__________MMS_Data_Type__ BIT Boolean Boolean [S_]BYTE Signed Integer 8 Signed Integer 8 [S_]WORD Signed Integer 16 Signed Integer 16 [S_]LONGWORD Signed Integer 32 Signed Integer 32 U_BYTE Unsigned Integer 8 Unsigned Integer 8 U_WORD Unsigned Integer 16 Unsigned Integer 16 U_LONGWORD Unsigned Integer 32 Unsigned Integer 32 F_FLOATING F-float Floating Point ARRAY[xx]:BIT Bit String Bit String STRING:xx Word Counted String Octet String ARRAY[xx]:format Array Array STRUCTURE Structure[1] Structure [1]The_maximum_number_of_fields_that_can_be_specified_in___ a structure is limited. The exact number of fields allowed is determined by the size of the fields, so is not an exact number. The DAS will return ILAN$_PEINVFMT if the maximum number of fields has been exceeded. ___________________________________________________________ In addition to the above supported mappings, additional mappings are possible by specifying a postfix operator on the BASEstar Classic physical point address. The postfix operator and the conversion performed is described in Table 3-3. 3-6 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions Table 3-3 DAS for DEComni Software Supported Address __________Postfix_Values___________________________________ Postfix Value_____DEComni_Data_Type_____MMS_Data_Type______________ \B Boolean[1] Boolean \O Word Counted Octet String String[2] \V Null Terminated Visible String String[3] \A Array[4] Array [1]This_form_allows_a_boolean_array_to_be_used_rather_than_ a bit string. [2]BASEstar Classic word and longword values are byte swapped before the values are returned to the user. [3]The BASEstar Classic data type must be STRING:xx. Visible Strings cannot be used as array elements. [4]Normally a variable defined as a structure in BASEstar Classic must be matched by a variable defined as a structure in the remote VMD. If this qualifier is used, the BASEstar Classic structure is simplified as much as possible. If the structure can be simplified to an array, then an array data type is used when defining the variable to DEComni. ___________________________________________________________ ________________________ Note ________________________ Postfix operators are not allowed for message physical points since for messages, no interpretation of the data is done by the DAS. ______________________________________________________ Using the DAS for DEComni Software 3-7 Using the DAS for DEComni Software 3.2 Supported Functions Example 3-3 shows an example of the information displayed after issuing the READ DATA command. Example 3-3 Read Data Screen DCM> read phy X/dev = TEST_PLC Point : X Device : TEST_PLC Address : n\X Format : S_LONGWORD Data: 0 : 2 DCM> Example 3-4 provides an example of the information displayed after issuing the READ DATA command when using data array. Example 3-4 Read Data Screen with Data Array DCM> read phy A/dev = TEST_PLC Point : A Device : TEST_PLC Address : n\A Format : ARRAY[4]:U_BYTE Data: 0 : 2 1 : 4 2 : 3 3 : 5 DCM> 3-8 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions Example 3-5 shows an example of the information displayed after issuing the WRITE DATA command. Example 3-5 Write Data Screen DCM> write phy X/dev = TEST_PLC Point : X Device : TEST_PLC Address : n\X Format : S_LONGWORD Data value 0 : 2 DCM> Example 3-6 shows an example of the information displayed after issuing the WRITE DATA command using data array. Example 3-6 Write Data Screen with Data Array DCM> write phy A/dev = TEST_PLC Point : A Device : TEST_PLC Address : n\A Format : ARRAY[4]:U_BYTE Data value 0 : 2 Data value 1 : 4 Data value 2 : 3 Data value 3 : 5 DCM> 3.2.4 SINEC-AP and SINEC-H1 Read and Write Message functions using ILAN$DEVICE_SPECIFIC The SINEC-AP and SINEC-H1 message functions are implemented as BASEstar Classic device specific functions. SINEC-AP messages can also be used with physical points. Using the DAS for DEComni Software 3-9 Using the DAS for DEComni Software 3.2 Supported Functions Table 3-4 lists ILAN$DEVICE_SPECIFIC function codes that are used to send and receive messages. Table_3-4_ILAN$DEVICE_SPECIFIC_Function_Codes______________ Function DEComni Code________function_________Description___________________ 5 omni_get_value Read a message from the remote VMD 6 omni_put_value Write a message to the remote VMD 7 omni_send_value Write a message to the remote VMD 8 omni_exchange_ Exchange a message with the ____________data_____________remote_VMD____________________ To write, send or exchange a message the ILAN$DEVICE_ SPECIFIC request buffer must be filled out according to the following syntax: message-name:message-length.text The message "text" will be written on the message "message- name" for the length "message-length". To read a message the ILAN$DEVICE_SPECIFIC request buffer must be filled out according to the following syntax: "message-name:message-length" The message "text" will be read from the message "message- name" for the length "message-length" and copied into the response buffer. Example 3-7 shows a C program reading a message. Example 3-7 Read message procedure (continued on next page) 3-10 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions Example 3-7 (Cont.) Read message procedure #include #include #define ILAN$K_READ_MSG 5 main() { $DESCRIPTOR (dev_dsc,"OMNI_DAS_SRV"); char req_buf[100]; char res_buf[100]; short req_len = 100; short res_len = 100; short ret_len; int func_code; long status; /* Read a message */ func_code = ILAN$K_READ_MSG; strcpy (req_buf,"OMNI_DAS_MSG:10"); memset (res_buf,0); /* clean up the buffer */ status = ILAN$DEVICE_SPECIFIC (0, &dev_dsc, &func_code, &req_len, req_buf, &res_len, res_buf, &ret_len); if (status != ILAN$_NORMAL) { /* error recovery as you like */ } printf ("Received message: %s\n",res_buf); } Using the DAS for DEComni Software 3-11 Using the DAS for DEComni Software 3.2 Supported Functions Example 3-8 shows a C program writing a message. Example 3-8 Write message procedure #include #include #define ILAN$K_WRITE_MSG 6 main() { $DESCRIPTOR (dev_dsc,"OMNI_DAS_SRV"); char req_buf[100]; char res_buf[100]; short req_len = 100; short res_len = 100; short ret_len; int func_code; long status; /* Write a message */ func_code = ILAN$K_WRITE_MSG; strcpy (req_buf,"OMNI_DAS_MSG:10.message !!"); /* "message !!" */ status = ILAN$DEVICE_SPECIFIC (0, &dev_dsc, &func_code, &req_len, req_buf, &res_len, res_buf, &ret_len); if (status != ILAN$_NORMAL) { /* ... */ } } 3-12 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions 3.2.5 SINEC-AP Read and Write Message Functions Using Physical Points When sending, receiving or exchanging a message, the first word of the buffer always contains the actual length of the data transferred. The maximum length of the message is the size of the physical point being defined. The DAS does no interpretation of the message that is transferred. Only one message can be created for a particular VMD. However, multiple physical points can be created for a particular device as long as the name of the message is identical. Also keep in mind that both a local and remote VMD can be created for a single device, and that a unique message can be created for each. For all solicited access, the message is created on the remote VMD with the exception of a physical point created with a "MW" address. For all unsolicited access, the message is created on the local VMD. 3.2.5.1 Reading a message To read a message from the remote VMD, an address of the form "M\YYY" must be specified where "YYY" is the name of the message. 3.2.5.2 Writing a message To write a message to the remote VMD, an address of the form "M\YYY" or "MW\YYY" must be specified where "YYY" is the name of the message. If "M" is specified, then the message is defined on the remote VMD and an acknowledged write is performed. If "MW" is specified, then the message is defined on the local VMD and an unacknowledged write is performed. Attempting to read from an address specified as "MW" results in an error being returned to the user. 3.2.5.3 Exchanging a message To exchange a message with the remote VMD, an address of the form "MX\YYY" must be specified where "YYY" is the name of the message. To exchange a message, a write must first be performed. The write fills in a buffer in the DAS with the data to be exchanged with the VMD. When a read is performed the message is exchanged and the resulting message is returned to the user. If multiple reads are Using the DAS for DEComni Software 3-13 Using the DAS for DEComni Software 3.2 Supported Functions performed without an intervening write, the same data is written to the remote VMD. 3-14 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions 3.2.6 Download, Upload and Directory Functions The upload function transfers the contents of a device's memory to an OpenVMS file. The download function transfers the contents of an OpenVMS file to a device's memory. The directory function lists a device's memory. In order to avoid errors, you will need to know how OpenVMS files are mapped onto the MMS device organization. DCM file services provide functionalities to operate on remote device files: file download, file upload, file directory and device program management. DEComni supports the MMS File Management Services (primitives FGET, FPUT, FDIR, FRENAME and FDELETE), however they are seldom supported by any of the modern MMS devices. Therefore, these primitives are not supported by the DAS for DEComni software. In this manual, a file is always intended to be a file storing data or instructions related to a Domain, ie. programs, and parameters. All operations on files are intended to operate on Domains and it is not possible, using the DAS for DEComni software to access the MMS file management primitives. The download function transfers the content of the VMS Domain and Capability files to a Domain. The upload function transfers the content of a Domain to the OpenVMS Domain and Capability files. The directory function lists the names of the Domains and the PIs found on a remote VMD. _________________ Domain Restrictions _________________ In general a Domain must first be uploaded from a device before it may be downloaded, this is due to vendor specific formatation of a devices Domain. Prior to a Domain being downloaded it must first be deleted at the remote MMS device, since the DAS for DEComni software does not support deleting of domains. ______________________________________________________ Example 3-9 shows an example of the information displayed after issuing the DIRECTORY command. Using the DAS for DEComni Software 3-15 Using the DAS for DEComni Software 3.2 Supported Functions Example 3-9 Directory Screen DCM> DIRECTORY GEF_PLC Directory of device GEF_PLC at 17-MAY-1991 09:30:47.46 Path: *.* Domain: I_O_OVERRIDE_TABLE Domain: I_O_TABLE Domain: REGISTER_TABLE Domain: SUBR_VECTOR_ADDRESSES Domain: USER_LOGIC PI : DEMO_PI Total of 6 files, size 0 DCM> Example 3-10 shows an example of the use of the UPLOAD and DOWNLOAD commands. Example 3-10 Upload and Download Screen DCM> UPLOAD GEF_PLC USER_LOGIC.DOM/DEV=USER_LOGIC DCM> ... DCM> DOWNLOAD GEF_PLC USER_LOGIC.DOM/DEV=USER_LOGIC DCM> The standard extension for the content file is .DOM: you can use any extension for the content file, the capability file has always the same name with extension .CAP. 3-16 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions 3.2.7 Start and Stop Functions The start and stop functions change the status of a Program Invocation. A Program Invocation can be reusable or not reusable. If a Program Invocation is reusable the start command will switch it from IDLE to RUNNING and the stop command will switch it from RUNNING to STOPPED and then to IDLE again. If a Program Invocation is not reusable the start command will switch it from IDLE to RUNNING and the stop command will switch it from RUNNING to STOPPED and then to UNRUNNABLE. To specify the Program Invocation name the OPTIONS field must be used with the following syntax: DCM> START dev_name /START_OPTIONS="PI=pi_name" and DCM> STOP dev_name /STOP_OPTIONS="PI=pi_name" A Program Invocation must exist on the device or created by the DAS for DEComni software. To create and delete program invocations the OPTION field must be used with the following syntax: DCM> START dev_name /START_OPTIONS="PI=pi_name,CREATE=dom_name" or DCM> START dev_name /START_OPTIONS="PI=pi_name,CREATE=(dom_name_list)" and DCM> STOP dev_name /STOP_OPTIONS="PI=pi_name,DELETE" The Program Invocations created by the DAS for DEComni software are always reusable. After a program terminates a START command can be entered again. After a program stop (error) a STOP command is needed before the program can be restarted. If a Program Invocation is idle a STOP/DELETE program will work anyway. Figure 3-1 shows the effects of the start and stop commands on a program invocation. Using the DAS for DEComni Software 3-17 Using the DAS for DEComni Software 3.2 Supported Functions Figure 3-1 Program Invocations State Table Please note that many state transactions cannot be done through the DAS for DEComni software. 3-18 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.2 Supported Functions 3.2.8 Read Status Function The read status function issues a diagnostic status request to the device, 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 you can perform an upload function or download function for the device. The BASEstar Classic Command Line Interface User's Guide gives detailed information about the READ STATUS command. To display the returned values for device status, enter the following at the BASEstar Classic prompt: DCM> READ STATUS device-name/FULL Figure 3-2 shows an example of the information displayed after issuing the READ STATUS command. Figure 3-2 Read Status Screen DCM> READ STATUS device-name/FULL Status of device GEF_PLC at 17-MAY-1991 09:29:04.70 Vendor: GE_Fanuc Model: SERIES_SIX_PC Revision: 0120_0311_0312 Physical status: 0 (Operational) Logical status: 0 (State Changes Allowed) Local detail: 00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000 DCM> 3.2.8.1 Logical Status Meaning The logical status of an MMS device tells a remote user, the DAS for DEComni software, the MMS services that it is capable of supporting. A user of the DAS for DEComni software, may check this status to determine why a particular service, his request, is returning an error condition. The logical status code values and their meaning are described in Table 3-5. Using the DAS for DEComni Software 3-19 Using the DAS for DEComni Software 3.2 Supported Functions Table_3-5_Logical_Status_Meaning___________________________ Logical_Status_Value__MMS_Meaning__________________________ 0 state changes allowed, all MMS services 1 no state changes allowed, Read Only services 2 limited services permitted, connect and status 3 supported services allowed, no PI ______________________services_____________________________ 3.2.8.2 Physical Status Meaning The physical status of an MMS device tells a remote user, the DAS for DEComni software, the generic capabilities and operational state of the hardware. Further meaning is outside the scope of the MMS specification and may be determined from the vendors local status details. The physical status code values and their meaning are described in Table 3-6. Table_3-6_Physical_Status_Meaning__________________________ Physical Status Value_________________MMS_Meaning__________________________ 0 Operational, ie. able to perform all tasks 1 Partially Operational, ie. not all tasks can be performed 2 Inoperable, ie. not operational _____3________________Needs_Commisioning,_ie._maintenance__ 3-20 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.3 Automatic Data Collection 3.3 Automatic Data Collection Data can be collected automatically through either polled or unsolicited data collection. These options are discussed in the following paragrahs. 3.3.1 Unsolicited Data Unsolicited data involves a device sending a physical point to BASEstar Classic services or reading a physical point from BASEstar Classic without it being previously requested. In both MMS and SINEC-AP/H1 this function is described as being either an Information Report, a Write Indication a Read Indication, or a Message Exchange Indication (SINEC-AP only). BASEstar Classic services can accept unsolicited values from any device as long as the device and physical point are defined with unsolicited information. Refer to the BASEstar Classic Command Line Interface User's Guide for more information concerning unsolicited data. Refer to the manufacturer's documentation for your specific device for more information on how it can send or request unsolicited data (Information Report, Write Indication or Read Indication). 3.3.1.1 Information Report DEComni devices are capable of sending unsolicited data to OpenVMS as Information Reports. The DAS for DEComni software allows you to define BASEstar Classic physical points for collecting unsolicited data. If the device sends up an Information Report the DAS forwards the message to BASEstar Classic. The BASEstar Classic unsolicited ID must equal "I\". Information reports are supported for named and unnamed variables and for SINCEC-AP messages. 3.3.1.2 Write Indication DEComni devices are capable of sending unsolicited data to OpenVMS as Write Indications. The DAS for DEComni software allows you to define BASEstar Classic physical points for collecting unsolicited data. If the device sends up a Write Indication the DAS forwards the message to BASEstar Classic. The BASEstar Classic unsolicited ID must equal "W\". Using the DAS for DEComni Software 3-21 Using the DAS for DEComni Software 3.3 Automatic Data Collection The difference between an Information Report and a Write Indication is in where the variable is defined. For an Information Report, the variable is defined on the Remote VMD. The Information Report sends the value of a variable that exists in the remote VMD. For a Write Indication, the variable is defined on the Local VMD. The Write Indication sends a value to the Local VMD from the remote peer. For a Write Indication, the variable does not need to exist on the Remote VMD. Write indications are supported for named and unnamed variables and for SINEC-AP messages. 3.3.1.3 Read Indication DEComni devices are capable of requesting unsolicited data from OpenVMS as Read Indications. The DAS for DEComni software allows you to define BASEstar Classic physical points for sending unsolicited data. It is possible to configure the physical point such that replies are automatically returned to the device, or to configure it such that an explicit write request must be sent to the device to complete a the read indication. These two options are discussed below. Read indications are supported for named and unnamed variables and for SINEC-AP messages. 3.3.1.3.1 Automatic Reply to Read Indication To automatically send a reply, a BASEstar Classic logical point must be associated with the physical point. If the device sends up a Read Indication the DAS reads the associated BASEstar Classic logical point and returns the result to the device. If the BASEstar Classic logical point does not exist or has a bad status, then an error is returned to the device. The BASEstar Classic unsolicited ID must equal "R\LOGICAL_POINT_NAME", where LOGICAL_POINT_ NAME is the name of the logical point to read to get the value to return to the device. The size of the format of the logical point must match the size of the data defined by the variable being requested by the Remote VMD. 3-22 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.3 Automatic Data Collection ________________________ Note ________________________ The logical point name is compiled when the variable is defined and the compiled name is used when accessing the data point when a Read Indication is detected. If the data manager global section is recreated, then the logical point name needs to be recompiled. To force recompiling of the logical point name delete the BCC$SYSDATA:ILAN$_SECTION.DAT global section backing file when restarting BASEstar Classic software. ______________________________________________________ The user can also request that a second point be updated when a BASEstar Classic logical point is read through a Read Indication. This capability allows an application to be notified when the Remote VMD has read a value from the OpenVMS system. The second point must have the same address as the Read Indication point with the addition of a "T\" prefix on the address and an unsolicited ID of "\T". The format of this physical point must be a "BIT". When a Read Indication occurs for the corresponding Read Indication point, the DAS forwards a message to BASEstar Classic with a value of "1". "Trigger" physical points are used only by the DAS and cannot be used to read or write values to a device. 3.3.1.3.2 Manual Reply to Read Indication There may be cases where the user wants to be notified of a read indication, and then send the reply to the device. In this case a "Trigger" physical point must be set up as described above for the automatic case. A physical point must also be configured with an unsolicited ID of "\R". Note that in this case there is no BASEstar Classic logical point name configured in the unsolicited ID. When a read indication is detected by the DAS, the corresponding trigger point for that physical point is updated. The user is then responsible for sending a write request to the DAS for the corresponding physical point associated with the trigger physical point. No further read indications for that physical point will be accepted until the previous Using the DAS for DEComni Software 3-23 Using the DAS for DEComni Software 3.3 Automatic Data Collection read indication has been completed by writing back down to the device. 3.3.1.4 Message Exchange Indication SINEC-AP devices are capable of exchanging unsolicited data with OpenVMS as Message Exchange Indications. The DAS for DEComni software allows you to define BASEstar Classic physical points for exchanging unsolicited data. It is possible to configure the physical point such that replies are automatically returned to the device, or to configure it such that an explicit write request must be sent to the device to complete a the message exchange indication. These two options are discussed below. Message exchange indications are supported for SINEC-AP messages only. 3.3.1.4.1 Automatic Reply to Exchange Message Indication To automatically send a reply, a BASEstar Classic logical point must be associated with the physical point. If the device sends up a Message Exchange Indication the DAS reads the associated BASEstar Classic logical point and returns the result to the device. If the BASEstar Classic logical point does not exist or has a bad status, then an error is returned to the device. The BASEstar Classic unsolicited ID must equal "X\LOGICAL_POINT_NAME", where LOGICAL_POINT_ NAME is the name of the logical point to read to get the value to return to the device. The size of the format of the logical point must match the size of the data defined by the message being requested by the Remote VMD. The data sent by the device is used to update the associated physical point. ________________________ Note ________________________ The logical point name is compiled when the message is defined and the compiled name is used when accessing the data point when a Message Exchange Indication is detected. If the data manager global section is recreated, then the logical point name needs to be recompiled. To force recompiling of the logical point name delete the BCC$SYSDATA:ILAN$_SECTION.DAT global 3-24 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.3 Automatic Data Collection section backing file when restarting BASEstar Classic software. ______________________________________________________ 3.3.1.4.2 Manual Reply to Message Exchange Indication There may be cases where the user wants to examine the message sent in a message exchange indication, and then send the reply to the device. In this case the physical point must be configured with an unsolicited ID of "\X". Note that in this case there is no BASEstar Classic logical point name configured in the unsolicited ID. When a message exchange indication is detected by the DAS, the corresponding physical point is updated. The user is then responsible for sending a write request to the DAS for the physical point. No further message exchange indications for that physical point will be accepted until the previous messge exchange indication has been completed by writing back down to the device. Table 3-7 summarizes unsolicited ID values and their meanings: Table_3-7_Unsolicited_ID_Values____________________________ Unsolicited_ID________Description__________________________ I\ Information Report W\ Write Indication R\LOGICAL_POINT_NAME Read Indication (Automatic Reply) R\ Read Indication (Manual Reply)[1] X\LOGICAL_POINT_NAME Message Exchange Indication (Automatic Reply) X\ Message Exchange Indication (Manual Reply) T\ Trigger [1]Note_that_in_this_case,_a_corresponding_"trigger"_______ physical point must be configured. ___________________________________________________________ Using the DAS for DEComni Software 3-25 Using the DAS for DEComni Software 3.3 Automatic Data Collection 3.3.1.5 Local and Remote VMDs Information Report and solicited variables and messages are defined on the Remote VMD only. Read and Write Indication variables and messages are defined on the Local VMD only. A Remote VMD is created in DEComni for each BASEstar Classic device. A Local VMD is created for each BASEstar Classic path definition. To force creation of a unique Local VMD for each Remote VMD, create a separate path for each device. Figure 3-3 shows an example of creating unsolicited physical point definitions. Figure 3-3 Unsolicited Point Definition DCM> create phy U1/dev=TEST_PLC/addr="N\U1"/form=long/unsol="I\" DCM> show phy U1/dev=TEST_PLC/FULL Physical Point : U1 Device : TEST_PLC Description : Address : N\U1 Data Format : S_LONGWORD Write Enabled : No Collection : Unsolicited ID : I\ Collection Enabled : No Distribution Destination Log : No BASEstar Classic Data Mgt : Number of Connections : 0 Defined on .... Definition last updated on .... DCM> (continued on next page) 3-26 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.3 Automatic Data Collection Figure 3-3 (Cont.) Unsolicited Point Definition DCM> create phy U2/dev=TEST_PLC/addr="N\U2"/form=long/unsol="R\P1" DCM> show phy U2/dev=TEST_PLC/FULL Physical Point : U2 Device : TEST_PLC Description : Address : N\U2 Data Format : S_LONGWORD Write Enabled : No Collection : Unsolicited ID : R\P1 Collection Enabled : No Distribution Destination Log : No BASEstar Classic Data Mgt : Number of Connections : 0 Defined on .... Definition last updated on .... DCM> DCM> create phy T2/dev=TEST_PLC/addr="T\N\U2"/form=BIT/unsol="T\" DCM> show phy T2/dev=TEST_PLC/FULL Physical Point : U2 Device : TEST_PLC Description : Address : T\N\U2 Data Format : S_LONGWORD Write Enabled : No Collection : Unsolicited ID : T\ Collection Enabled : No Distribution Destination Log : No BASEstar Classic Data Mgt : Number of Connections : 0 Defined on .... Definition last updated on .... DCM> (continued on next page) Using the DAS for DEComni Software 3-27 Using the DAS for DEComni Software 3.3 Automatic Data Collection Figure 3-3 (Cont.) Unsolicited Point Definition DCM> create phy M1/dev=TEST_PLC/addr="M\M1" - _DCM> /form=struct"(array[10]:WORD)"/unsol="W\" DCM> show phy M1/dev=TEST_PLC/FULL Physical Point : M1 Device : TEST_PLC Description : Address : M\M1 Data Format : S_LONGWORD Write Enabled : No Collection : Unsolicited ID : W\ Collection Enabled : No Distribution Destination Log : No BASEstar Classic Data Mgt : Number of Connections : 0 Defined on .... Definition last updated on .... DCM> 3.3.2 Pollsets/Scattered Read BASEstar Classic physical points may be grouped together into pollsets to optimize data collection and to provide the ability to read a group of points on a specified time interval. DCM allows you to read groups of physical points (variables) using the scattered pollset feature. Any combination of physical points may be included in a pollset. The use of the /SCATTERED qualifier is mandatory when creating the pollset. Figure 3-4 shows an example of creating a scattered pollset for reading groups of named variables. Figure 3-4 Scattered Pollset Definition (continued on next page) 3-28 Using the DAS for DEComni Software Using the DAS for DEComni Software 3.3 Automatic Data Collection Figure 3-4 (Cont.) Scattered Pollset Definition DCM> create pollset POLL1/device=TEST_PLC/interval=15/scattered DCM> create phypoint P1/dev=TEST_PLC/format=long/addr=VMD_INT32 - _DCM> /poll=POLL1/COLLECT DCM> create phypoint P2/dev=TEST_PLC/format=word/addr=OSAPWORD - _DCM> /poll=POLL1/COLLECT DCM> SHOW POLL */DEV=TEST_PLC/FUL Device Name : TEST_PLC Pollset Name: POLL1 Interval : 15 Enabled : No Format : SCATTERED Start Address : VMD_INT32 Number elements : 2 IO blocks : 1 Size (in bytes) : 6 Buffers not dist: 0 Defined on .... Definition last updated on .... Permanent Lka Ctr :0 Temporary Lka Ctr :0 Permanent Late Ctr :0 Temporary Late Ctr :0 Permanent Device Errors :0 Temporary Device errors :0 Permanent No Buffers errors :0 Temporary No Buffers errors :0 BASEstar Classic point name: DCM Phypoint name: P1 P2 DCM> This service provides the equivalent of calling the omni_ group_variable service for each physical point (variable) in the pollset. For more information on physical points, see the BASEstar Classic Command Line Interface User's Guide. Using the DAS for DEComni Software 3-29 A _________________________________________________________________ The DAS for DEComni Software Returned Values and Associated Error Messages If a BASEstar Classic command returns back ILAN$_PEERRCMD, ILAN$_PECHECKLOG or another error related to the device look please at the history file. You will find a log message like: Event 10.87.19 occurred at 31-OCT-1991 08:45:19.18 OMNI_pe_access - OMNI_CONNECT returned :%OMNI-E-INITFAIL, Initiate Request Failed Sometimes you will also find an additional log message about NETWORK or PROVIDER: Event 10.87.19 occurred at 31-OCT-1991 08:45:19.30 OMNI_pe_access - OMNI returned also NETWORK status :%OSAP-E-ASONOTCREA, Association not Created For a full list of DEComni errors please refer to the DEComni Application Interface User's Guide. This is a short guide to the most commonly seen errors. OMNI-E-NOCP, OMNI Control Process not found, Explanation: Error. You tried to start DCM without first starting DEComni/DECosap. User Action: Check DEComni/DECosap availability. OMNI-E-INITFAIL, Initiate request failed, Explanation: Error. You tried to connect to a device. User Action: Check the device availability. OMNI-E-CONNECTERR, Connect Error, Explanation: Error. You tried to connect to a device. User Action: Check local and remote ODS configurations. If using the AST shared image, make sure that you are using the supplied ILAN$SYSTEM_STARTUP. for DEComni Software Returned Values and Associated Error Messages A-1 The DAS for DEComni Software Returned Values and Associated Error Messages OMNI-E-OBJ_UNDEFINED, Service Error Class- Definition: Object Undefined, Explanation: Error. You tried to read/write a variable. User Action: Check that the variable is defined at the remote device. OMNI-E-OBJ_ACCESS_DENIED, Service Error Class- Access: Denied, Explanation: Error. You tried to access a device variable. User Action: Check the variable address on the device. OMNI-E-GETVAL_CNR_ERR, Get Value Confirm Error, Explanation: Error. You tried to read a device variable. User Action: Check the variable read permission on the device. OMNI-E-PUTVAL_CNR_ERR, Put Value Confirm Error, Explanation: Error. You tried to write a device variable. User Action: Check the variable write permission on the device. OMNI-E-OBJ_NOT_EXISTEN, Service Error Class- Access: Non- Existent, Explanation: Error. You referred to a nonexistent Domain or PI. User Action: Issue a DIRECTORY command to find valid Domains and PIs. OMNI-E-STARTPI_REQ_ERR, Start Program Invocation Request Service Error, Explanation: Error. You tried to start a PI but probably you did not specify the /START_OPTIONS qualifier. User Action: Specify /START_OPTIONS qualifier in your start command. OMNI-E-RESETPI_REQ_ERR, Reset Program Invocation Request Service Error, Explanation: Error. You tried to stop a PI but probably you did not specify the /STOP_OPTIONS qualifier. User Action: Specify the /STOP_OPTIONS qualifier on your stop command. A-2 The DAS for DEComni Software Returned Values and Associated Error Messages DAS for DEComni Software Returned Values and Associated Error Messages OMNI-E-OBJ_STATE_CONFL, Service Error Class- Service: Object State Conflict, Explanation: Error. You probably tried to start or to stop a PI twice. User Action: None. OMNI-F-INVFUNC, Connection is not in a valid state for this ..., Explanation: Fatal. You have probably defined the device as "/NOUNSOL" and the device or Network has aborted or concluded the connection. User Action: Define the device as /UNSOL. OMNI-E-GET-CAPABILITY, Get Capability List Confirm Error, Explanation: Error. You tried to read a devices status. User Action: Check that the device is still running. OSAP-E-ASONOTCRE, Association not created, Explanation: Error. You tried to connect to a device. User Action: Check local and remote configurations. for DEComni Software Returned Values and Associated Error Messages A-3 _________________________________________________________________ Index A Device Access Software _______________________________ (cont'd) Accessing DAS functions, 3-1 installation of, 2-1 Additional software installation requirements, required, 2-2 2-1 Application Simple Name, 2-17 MMS functions, 3-2 Automatic data collection, overview, 1-1 3-21 SINEC-AP functions pollsets, 3-28 SINEC-H1 functions, 3-2 unsolicited data, 3-21 supported devices, 3-2 supported functions, 1-3, C______________________________ 3-2 Configuration using, 3-1 NCL, 2-30 Device records, 2-18 ODS, 2-20 Devices Configuration file communications, 1-2 device records, 2-18 Directory function, 3-15 example, 2-23 Disk space required, 2-3 path records, 2-17 Download function, 3-15 type records, 2-15 Configuration File E______________________________ editing, 2-15 Exchange message function, D 3-9, 3-13 _______________________________ Exchange message indication DAS automatic reply, 3-24 See Device Access Software Data types, 3-5 F______________________________ Defining DAS Constants, 2-15 Files Device Access Software created during installation, accessing functions, 3-1 2-10 defining constants, 2-15 description of, 1-1 functions, 1-3, 1-5 Index-1 Functions, 3-1 device specific, 3-9, 3-13 N______________________________ directory, 3-15 NCL configuration, 2-30 download, 3-15 exchange message, 3-9, 3-13 O read data, 3-4 _______________________________ read message, 3-9, 3-13 ODS Configuration, 2-20 read status, 3-19 OSI Tracing, 2-32 start, 3-17 stop, 3-17 P______________________________ upload, 3-15 Path records, 2-17 write data, 3-4 Pollsets, 3-28 write message, 3-9, 3-13 Post installation tasks, 2-13 Problem reporting, 2-32 G______________________________ Product failure, 2-32 Group Reads, 3-28 Protocol Profile, 2-17 _______________________________ R______________________________ Hardware Read data function, 3-4 required, 2-1 Read indication, 3-22 automatic reply, 3-22 I______________________________ manual reply, 3-23 Information report, 3-21 Read message function, 3-9, Installation, 2-1 3-13 files created, 2-10 Read status function, 3-19 messages, 2-11 Remote VMD, 3-26 post installation tasks, S 2-13 _______________________________ procedure, 2-4 Scattered Read, 3-28 requirements, 2-1 Shop floor equipment setting up, 2-32 L______________________________ Sinec-AP Local VMD, 3-26 message support, 3-13 Sinec-AP and SINEC-H1 specific functions, 3-9 M______________________________ Software Message exchange indication, required, 2-2 3-24 Specific functions manual reply, 3-25 device, 3-9 Messages SPT block usage, 2-31 installation, 2-11 Start function, 3-17 Stop function, 3-17 Index-2 SYSGEN parameters, 2-14 message exchange indication, 3-24 T______________________________ read indication, 3-22 Tracing write indication, 3-21 OSI messages, 2-32 Upload function, 3-15 Tuning ILAN$DEVSRV, 2-14 W Type records, 2-15 _______________________________ Write data function, 3-4 U______________________________ Write indication, 3-21 Unsolicited data, 3-21 Write message function, 3-9, information report, 3-21 3-13 Index-3