BASEstar Open Device Connectivity Device Access Software for Siemens 3964 User Guide Order Number: AA-QT1RB-TE April 1997 April 1997 April 1997 This document describes the Device Access Software (DAS) for Siemens 3964 which allows BASEstar Open users and DEComni API applications to exchange data with Siemens devices supporting the Siemens 3964 protocols. Revision/Update Information Revision/Update Information Revision/Update Information: This is a new document for the current release. Operating System and Version Operating System and Version Operating System and Version: BASEstar Open is available on a broad range of both hardware and software platforms. Refer to your Software Product Description for precise information. Software Version: Software Version: Software Version: 3.1 Digital Equipment Corporation Digital Equipment Corporation Digital Equipment Corporation Maynard, Massachusetts Maynard, Massachusetts Maynard, Massachusetts First printing, February 1996 First printing, February 1996 First printing, February 1996 Revised, July 1996 Revised, July 1996 Revised, July 1996 Revised, April 1997 Revised, April 1997 Revised, April 1997 c Digital Equipment Corporation 1997. All Rights Reserved. Possession, use, or copying of the software described in this documentation 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. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, BASEstar Open, DEC, DECmessageQ, DECnet, DECnet-DOS, DECosap, DEComni, DIGITAL, DIGITAL UNIX, FMS, LN03, MicroVAX, NAS, OpenVMS, OpenVMS Alpha, PATHWORKS, PDAS, Rdb/VMS, ReGIS, ThinWire, TK, ULTRIX, VAX, VAXcluster, VAX COBOL, VAX FORTRAN, VAX Pascal, VAX RMS, VMS/ULTRIX Connection, VT, and the DIGITAL logo. The following are third-party trademarks: MS, Microsoft, and MS-DOS are registered trademarks of Microsoft Corporation. UNIX is a registered trademark licensed exclusively by X/Open Company Ltd. Windows and Windows NT are trademarks of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective holders. Table of Contents Table of Contents Table of Contents Preface Preface Preface ................................ ................................ ................................................... ................... ...................viii viii viii 1 Introduction 1 Introduction 1 Introduction ................................ ................................ ............................................ ............ ............ 1 1 1 - - - 1 1 1 Communicating With Siemens 3964 Devices.................1-1 Features of the DIGITAL DAS for Siemens 3964............ 2 - 1 What's Next?............................................ 4 - 1 2 Installing the DAS for Siemens 3964 on Your Platform 2 Installing the DAS for Siemens 3964 on Your Platform 2 Installing the DAS for Siemens 3964 on Your Platform ..... ..... .....2 2 2- - -1 1 1 Installation on DIGITAL UNIX Systems.................... 2 - 2 Preparing for DAS for Siemens 3964 Installation ...... 2 - 2 Installing the DAS for Siemens 3964 .................. 5 - 2 Getting Help and Reporting Problems .................. 5 - 2 Installation on Windows NT Systems...................... 7 - 2 Preparing for DAS for Siemens 3964 Installation ...... 7 - 2 Installing the DAS for Siemens 3964 .................. 8 - 2 Deinstalling the DAS for Siemens 3964 ................ 8 - 2 Getting Help and Reporting Problems .................. 8 - 2 Installation on OpenVMS Systems........................ 10 - 2 Preparing for DAS for Siemens 3964 Installation ..... 10 - 2 Installing the DAS for Siemens 3964 .................2 12 - Getting Help and Reporting Problems ................. 13 - 2 PART I Using BASEstar Open to Communicate With Siemens 3964 PART I Using BASEstar Open to Communicate With Siemens 3964 PART I Using BASEstar Open to Communicate With Siemens 3964 Devices Devices Devices 3 Overview 3 Overview 3 Overview ................................ ................................ ................................................. ................. ................. - - - 3 3 3 1 1 1 BASEstar Open Environment Components.................... -2 3 Exchanging Data Messages With a Siemens 3964 Device (3964[R] Protocol)....................................... 4 - 3 Sending Data ......................................... - 3 4 Receiving Data .......................................3-5 Accessing the Memory of a Siemens 3964 Device (3964[R]_RK512 Protocol)................................. 6 - 3 Emulating a Siemens 3964 Device (3964[R]_RK512 Protocol) 8 3- Datatypes and Memory Block Sizes........................3 8 - 4 Configuring BASEstar Open 4 Configuring BASEstar Open 4 Configuring BASEstar Open ................................ ................................ ................................ - - - 4 4 4 1 1 1 iii Registering ODS Entries .................................4 2 - Creating Application Services Objects ...................4 2 - Creating Device Services Objects ........................4-2 Creating Protocol_Profiles ...........................4 2 - Creating VMDs ................................ 4 ........ 3 - Creating Variables ...................................4 7 - Creating Data Services Objects ..........................4 9 - Creating Device_Data_Points for Communication Via the 3964[R] Protocol ................................ 4 ...... 9 - Creating Device_Data_Points for Communication Via the 3964[R]_512 Protocol ................................ - 4 . 11 5 Examples 5 Examples 5 Examples ................................ ................................ ................................................. ................. .................5 5 5 1 1 1 - - - Example 1: Using the 3964[R] Protocol to Exchange Data 5 .. -2 Example Overview ................................ 5 ..... 2 - Before Running the Example ...........................5 2 - CLI Source ...........................................5 2 - Example 2: Accessing the Memory of a Siemens 3964 Device (3964[R]_RK512 Protocol) ................................ 5 . 7 - Example Overview ................................ 5 ..... 7 - Before Running the Example ...........................5 7 - CLI Source ...........................................5 7 - Example 3: Emulating a Siemens 3964 Device (3964[R]_RK512 Protocol) ............................................... - 5 11 Example Overview ................................ - 5 .... 11 Before Running the Example .......................... - 5 11 CLI Source ..........................................5-11 PART II Using the DEComni API to Communicate With Siemens 3964 PART II Using the DEComni API to Communicate With Siemens 3964 PART II Using the DEComni API to Communicate With Siemens 3964 Devices Devices Devices 6 Overview 6 Overview 6 Overview ................................ ................................ ................................................. ................. .................6 6 6 1 1 1 - - - DEComni API Environment Components ......................6 2 - Exchanging Data Messages With a Siemens 3964 Device (3964[R] Protocol) .......................................6 3 - Receiving Data ................................ 6 ....... -3 Sending Data Messages ................................6-4 Accessing the Memory of a Siemens 3964 Device (3964[R]_RK512 Protocol) .................................6-4 Emulating a Siemens 3964 Device (3964[R]_RK512 Protocol) 6-5 MMS Types and Siemens 3964 Memory Block Sizes ...........6-6 7 Configuring DEComni API 7 Configuring DEComni API 7 Configuring DEComni API ................................ ................................ .................................. .. ..7 7 7- - -1 1 1 Registering ODS Entries ................................ 7 . 2 - Setting the Application Profile .........................7 2 - Creating VMD Definitions ................................7 2 - Using the 3964[R] Protocol to Create a VMD for Communication ................................ 7 ......... 3 - Using the 3964[R]_RK512 Protocol to Create a VMD for Communication .........................................7-3 Creating Variable Definitions ...........................7 3 - iv Using the 3964[R] Protocol to Create Variables for Communication ......................................... - 7 4 Using the 3964[R]_RK512 Protocol to Create Variables for Communication ......................................... 5 - 7 8 Programming 8 Programming 8 Programming ................................ ................................ .............................................. .............. ..............8-1 8-1 8-1 Programming With the 3964[R] Protocol...................8-2 Opening a Connection ................................ 8-2 . Sending Data Messages ................................8-3 Receiving Data Messages ..............................8-3 Programming With the 3964[R]_RK512 Protocol.............8-3 Opening and Closing a Connection .....................8-5 Reading and Writing Memory Blocks of a Siemens Device 8-5 Fulfilling Requests for an Emulated Device ...........8-6 PART III Appendices PART III Appendices PART III Appendices A ODS Entry Attributes for the Siemens 3964 Protocol A ODS Entry Attributes for the Siemens 3964 Protocol A ODS Entry Attributes for the Siemens 3964 Protocol ....... ....... ....... 1 1 1 - - - A A A Creating ODS Entries for the Siemens 3964 Protocol....... 2 - A Configuring a LAT Port................................... 4 - A OpenVMS Platform ...................................... -4 A DIGITAL UNIX Platform ................................. - A 4 B BASEstar Open Datatype Sizes B BASEstar Open Datatype Sizes B BASEstar Open Datatype Sizes ............................. ............................. ............................. 1 1 1 - - - B B B C DEComni MMS Type Sizes C DEComni MMS Type Sizes C DEComni MMS Type Sizes ................................ ................................ ................................... ... ... - - - C C C 1 1 1 E DEComni API Network IOSB Messages E DEComni API Network IOSB Messages E DEComni API Network IOSB Messages ........................ ........................ ........................E-1 E-1 E-1 v Figures Figures Figures Figure 1-1: Software Components for Siemens 3964 Communication ............................................1-1 Figure 1-2: Communicating With Siemens 3964 Devices 1 ...... 2 - Figure 3-1: BASEstar Open Environment Components .........3 2 - Figure 3-2: BASEstar Open Objects and Operations (3964[R] Protocol) ................................................3 4 - Figure 3-3: Using BASEstar Open to Access the Memory of a Siemens 3964 Device ................................ 3 ...... -6 Figure 3-4: Using BASEstar Open to Emulate a Siemens 3964 ................................ Device ...................3 8 - Figure 6-1: DEComni API Environment Components ...........6 2 - Figure 6-2: DEComni Definitions and API Procedures (3964[R] Protocol) ................................................6 3 - Figure 6-3: Using the DEComni API to Access the Memory of a Siemens 3964 Device ................................ 6 ...... 5 - Figure 6-4: Using the DEComni API to Emulate a Siemens 3964 ................................ Device ...................6 6 - Tables Tables Tables Table 1-1: Supported Siemens 3964 Protocols ..............1 2 - Table 2-1: Pre-requisite Software for DIGITAL UNIX (BASEstar Open Environment) ................................ 2 ........ 3 - Table 2-2: Pre-requisite Software for DIGITAL UNIX (DEComni API Environment) ................................ 2 ......... 4 - Table 2-3: Pre-requisite Software for Windows NT 2 ......... 7 - Table 2-4: Pre-requisite Software for OpenVMS (BASEstar Open Environment) ............................................ - 2 11 Table 2-5: Pre-requisite Software for OpenVMS (DEComni API Environment) ............................................ - 2 11 Table 2-6: Transport Network Software ................... - 2 12 Table 4-1: Protocol_Profile Attributes ...................4 3 - Table 4-2: VMD Attributes ................................4 4 - Table 4-3: Reception Variable Attributes (3964[R] Protocol) 7 - 4 Table 4-4: Transmission Variable Attributes (3964[R] Protocol) ................................................4-8 Table 4-5: Variable Attributes (3964[R]_RK512 Protocol) 4 .. -9 Table 4-6: Device_Data_Point Attributes for Receive Operations (3964[R] Protocol) ...........................4-10 Table 4-7: Device_Data_Point Attributes for Send Operations (3964[R] Protocol) ......................................4-11 Table 4-8: Device_Data_Point for Send and Receive Operations (3964[R]_512 Protocol) ................................ - 4 .. 11 Table 7-1: DEComni Application Profiles ..................7 2 - Table 7-2: DEComni VMD Attributes ........................7 2 - Table 7-3: DEComni Variable Attributes ...................7 4 - Table 8-1: DEComni API Procedures for Data Exchange (3964[R] Protocol) ................................................8-2 Table 8-2: DEComni API Procedures for Data Exchange (3964[R]_512 Protocol) ................................ 8-4 ... Examples Examples Examples vi Example 4-1: Creating Device Services Protocol_Profiles - 4 .. 3 Example 4 2: Creating a Device Services VMD (3964[R] - Protocol)................................................4-5 Example 4 3: Creating Device Services VMDs (3964[R]_RK512 - Protocol)................................................ 6 - 4 Example 5 1: Creating BASEstar Open Objects - (3964[R] Protocol)................................................ 3 - 5 Example 5 2: Exchanging Data with a Siemens 3964 Device - (3964[R] Protocol)....................................... 5 - 5 Example 5 3: Creating BASEstar Open Objects (3964[R]_RK512 - Protocol)................................................ 7 - 5 Example 5 4: Reading and Writing the Device Memory - (3964[R]_RK512 Protocol)................................ 10 - 5 Example 5-5: Parameter File (3964[R]_RK512 Protocol).... -11 5 Example 5-6: Emulating a Siemens 3964 Device (3964[R]_RK512 Protocol)............................................... - 5 12 Example 5-7: Reading and Writing the Emulated Device Memory (3964[R]_RK512 Protocol)................................ 15 - 5 Example A 1: ODS Entry for LAT Port - ...................... 3 - A vii Preface Preface Preface This document describes how to install and use the DIGITAL Device Access Software (DAS) for Siemens 3964, the software that allows BASEstar Open users and DEComni API applications to exchange data with Siemens 3964 devices that support the Siemens 3964 protocols. Multiplatform Applicability Multiplatform Applicability Multiplatform Applicability Most of the information in this manual applies regardless of the operating system platform on which the DAS for Siemens 3964 software is installed. Information relating to installation is typically platform-dependent. Intended Audience Intended Audience Intended Audience This manual is addressed to: System managers who have to install and maintain the DAS for Siemens 3964 on any of the supported platforms. Application developers who have to configure and use BASEstar Open, or the DEComni API (or both) to exchange data with Siemens 3964 devices. Structure of this Document Structure of this Document Structure of this Document This document is organized as follows: Chapter 1 introduces you to the DAS for Siemens 3964; Chapter 2 contains the installation procedures. Part I describes how Siemens 3964 devices are accessed via BASEstar Open services, how you must configure BASEstar Open for use with the DAS for Siemens 3964, and finally provides code examples that you can run in the BASEstar Open environment. Part II describes how to access Siemens 3964 devices via the DEComni API, how to configure DEComni API for use with the DAS for Siemens 3964, and how to exchange data with the remote devices. Part III contains the appendices. viii For More Information For More Information For More Information If you are using BASEstar Open services you will find related information in the following documents: BASEstar Open Introduction BASEstar Open Reference Guide BASEstar Open Command Language Interface BASEstar Open Application Programming Interface BASEstar Open Messages Platform-specific management guides If you are using DEComni API you will find related information in the following document: DEComni API and DEComni MMS User Guide DEComni API Guide to Using Omni Directory Services (for supported platforms) DEComni API Omni Definition Facility User Guide (for supported platforms) DEComni API Guide to Using OmniView (for supported platforms) ix 1 1 1 Introduction Introduction Introduction The DIGITAL Device Access Software (DAS) for Siemens 3964 allows both BASEstar Open users and DEComni API applications to access Siemens 3964 devices that support the 3964 protocols. Communicating With Siemens 3964 Devices Communicating With Siemens 3964 Devices Communicating With Siemens 3964 Devices Figure 1-1 shows how a system equipped with the BASEstar Open or the DEComni API product can communicate with a Siemens 3964 device using the Siemens 3964 protocols. The system equipped with BASEstar Open or DEComni API is an OpenVMS or DIGITAL UNIX system. Figure Figure Figure 1 1 1 : Software Components for Siemens 3964 : Software Components for Siemens 3964 : Software Components for Siemens 3964 1 1 1 - - - Communication Communication Communication As illustrated in Figure 1-2, a system (and thus BASEstar Open users or DEComni API applications) can communicate with Siemens 3964 devices connected to a RS-232 port or to a terminal server via an Ethernet LAN. The system can connect several Siemens 3964 devices by means of a point-to-point connection. Device Access Software for Siemens 3964 User Guide 1 1 1 1 1 1- - - Introduction Figure Figure Figure 1 1 1 2 2 2: Communicating With Siemens 3964 Devices : Communicating With Siemens 3964 Devices : Communicating With Siemens 3964 Devices - - - Features of the DIGITAL DAS for Siemens 3964 Features of the DIGITAL DAS for Siemens 3964 Features of the DIGITAL DAS for Siemens 3964 The DIGITAL DAS for Siemens 3964 allows BASEstar Open users and DEComni API applications to: Exchange data messages with a Siemens 3964 device using the Siemens 3964[R] protocol. Access memory blocks on a Siemens 3964 device using the Siemens 3964[R]_RK512 protocol. The main features of the supported protocols are listed in Table 1-1. In addition, a system equipped with BASEstar Open or DEComni API can emulate Siemens 3964 devices that accept and fulfill requests received from remote devices via the Siemens 3964[R]_RK512 protocol. Table Table Table - - - 1 1 1 1 1 1: Supported Siemens 3964 Protocols : Supported Siemens 3964 Protocols : Supported Siemens 3964 Protocols Protocol Protocol Protocol Features Features Features Version Version Version Siemens 3964 The Siemens 3964 protocol allows the exchange of data messages between your BASEstar Open or DEComni API system and a Siemens device. 1 1 1 Device Access Software for Siemens 3964 User Guide 2 2 2 - - - Introduction Siemens The Siemens 3964R protocol is like 3964R the Siemens 3964 protocol but the Block Check Character (BCC) is also supported. Siemens The RK512 interpreter is layered 3964_RK512 above the Siemens 3964 protocol. This allows direct and named access to device memory blocks. Siemens Same as Siemens 3964_RK512 but the 3964R_RK512 RK512 interpreter is layered above the Siemens 3964R protocol. Device Access Software for Siemens 3964 User Guide 1 1 1- - -3 3 3 Introduction What's Next? What's Next? What's Next? In this chapter you have learnt about the features of the DIGITAL DAS for Siemens 3964. If you intend to use the DAS for Siemens 3964 via BASEstar Open services, first read Chapter 2 to know how to install the DAS for Siemens 3964 on your system, and then read Part I of this manual to know how you must configure BASEstar Open and use its services to exchange data with Siemens 3964 devices. If you intend to use the DAS for Siemens 3964 via the DEComni API, read Chapter 2 for information about how to install the DAS for Siemens 3964 on your system. Then read Part II of this manual for details of how to configure the DEComni API and use the API procedures to exchange data with Siemens 3964 devices. 1 1 1 - - -4 4 4 Device Access Software for Siemens 3964 User Guide 2 2 2 Installing the DAS for Siemens 3964 on Your Platform Installing the DAS for Siemens 3964 on Your Platform Installing the DAS for Siemens 3964 on Your Platform This chapter specifies the requirements and the procedures for installing the DAS for Siemens 3964 on the following platforms: DIGITAL UNIX Windows NT OpenVMS The chapter provides the instructions for installing the DAS for Siemens 3964 in the BASEstar Open and DEComni API environments. Device Access Software for Siemens 3964 User Guide 1 1 1 2 2 2 - - - Installing the DAS for Siemens 3964 on Your Platform Installation on DIGITAL UNIX Systems Installation on DIGITAL UNIX Systems Installation on DIGITAL UNIX Systems The installation requirements vary depending on whether you are installing the DAS for Siemens 3964 for use via BASEstar Open services or via the DEComni API. Preparing for DAS for Siemens 3964 Installation Preparing for DAS for Siemens 3964 Installation Preparing for DAS for Siemens 3964 Installation Before starting the installation procedure, complete the preparation requirements outlined in this section. Release Notes Release Notes Release Notes Your documentation includes the Device Access Software for Siemens 3964 Release Notes, which you should read before installing and using the product. The release notes may contain information about changes to the application. After you install the Device Access Software for Siemens 3964 software, you can also access the online release notes in the form of an ASCII text file by entering the following command: # more /usr/opt/DASS3964_310/doc/relnotes.txt License Registration License Registration License Registration The Device Access Software for Siemens 3964 includes support for the DIGITAL UNIX License Management Facility (LMF). A License Product Authorization Key (License PAK) must be registered in the License Database (LDB) in order to use the Device Access Software for Siemens 3964 on a newly-licensed node. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing the Device Access Software for Siemens 3964 as an update on a node already licensed for this software, you have already completed the License PAK registration requirements. If you are installing pre-requisite or optional software along with the Device Access Software for Siemens 3964, review the PAK status and install the PAKs for any pre-requisite or optional software before you install the Device Access Software for Siemens 3964. To register a license under the DIGITAL UNIX system, first log in as superuser. You then have a choice of two ways to perform the PAK registration in the License Database (LDB): - - -2 2 2 2 2 2 Device Access Software for Siemens 3964 User Guide Installing the DAS for Siemens 3964 on Your Platform Before installing the Device Access Software for Siemens 3964 At the superuser prompt, edit an empty PAK template with the lmf register command and include all the information on your License PAK as follows: # lmf register After installing the Device Access Software for Siemens 3964 At the superuser prompt, edit the partially completed PAK template in /usr/var/adm/lmf/template with the lmf register command to add your unique License PAK information as follows: # lmf register - < /usr/var/adm/lmf/DAS3964 After you register your license, use the following lmf reset command to copy the license details from the License Database (LDB) to the kernel cache: # lmf reset For complete information on using the DIGITAL UNIX License Management Facility, see the DIGITAL UNIX Guide to Software Licensing or the lmf(8) reference page. Software Requirements (BASEstar Open Environment) Software Requirements (BASEstar Open Environment) Software Requirements (BASEstar Open Environment) If you are installing the DAS for Siemens 3964 in the BASEstar Open environment, check that the software products listed in Table 2-1 have been installed appropriately on your system. - - - Table Table Table 2 2 2 : Pre-requisite Software for DIGITAL UNIX : Pre-requisite Software for DIGITAL UNIX : Pre-requisite Software for DIGITAL UNIX 1 1 1 (BASEstar Open Environment) (BASEstar Open Environment) (BASEstar Open Environment) Subset Name and Subset Name and Subset Name and Comments Comments Comments Description Description Description OSFLAT200 Install this product to DEC TCP/IP Services for make LAT support available DIGITAL UNIX Version to DAS for Siemens 3964. 3.1 BSTR310 Ensure that the BASEstar BASEstar Open Server Open Device Connectivity for DIGITAL UNIX (DEComni) has been Version 3.1 installed. Device Access Software for Siemens 3964 User Guide - - -3 3 3 2 2 2 Installing the DAS for Siemens 3964 on Your Platform In particular, check for the presence of the following subsets: DOUBASE310 DASTK232310 DASTKRUN310 See the BASEstar Open Server Inst. and Management for your platform for Guide details. Software Requirements (DEComni API Environment) Software Requirements (DEComni API Environment) Software Requirements (DEComni API Environment) If you are installing the DAS for Siemens 3964 in the DEComni API environment, check that the software products listed in Table 2-2 have been installed on your system. Table Table Table 2 2 2 - - - 2 2 2 : Pre-requisite Software for DIGITAL UNIX : Pre-requisite Software for DIGITAL UNIX : Pre-requisite Software for DIGITAL UNIX (DEComni API Environment) (DEComni API Environment) (DEComni API Environment) Subset Name and Subset Name and Subset Name and Comments Comments Comments Description Description Description DOUBASE310 In particular, check for DEComni API for the presence of the DIGITAL UNIX Version following subsets: 3.1 DASTK232310 DASTKRUN310 See the DEComni API Installation Guide for your platform for details. OSFLAT200 Install this product to DEC TCP/IP Services make LAT support available for DIGITAL UNIX to DAS for Siemens 3964. Version 3.1 Disk Space Requirements Disk Space Requirements Disk Space Requirements The following table lists the disk space required to install the DAS for Siemens 3964. Usage Usage Usage (root) (root) (root) /usr/opt /usr/opt /usr/opt /var/opt /var/opt /var/opt (Kbytes) (Kbytes) (Kbytes) Installation 0 1103 381 2 2 2 4 4 4 Device Access Software for Siemens 3964 - - - User Guide Installing the DAS for Siemens 3964 on Your Platform Permanent 0 1103 339 Backing Up Your System Disk Backing Up Your System Disk Backing Up Your System Disk DIGITAL recommends that you back up your system disk before installing any software. For information about how to perform a system disk backup, refer to your DIGITAL UNIX documentation. Installing the DAS for Siemens 3964 Installing the DAS for Siemens 3964 Installing the DAS for Siemens 3964 This section describes the installation, deinstallation and IVP procedures for the Device Access Software for Siemens 3964 for DIGITAL UNIX. Installing the Device Access Software for Siemens 3964 and running the Installation and Verification Procedure (IVP) on your DIGITAL UNIX system takes approximately 5 to 10 minutes. Installation Procedure Installation Procedure Installation Procedure Install the DAS for Siemens 3964 as follows: Log onto the system as superuser (root). 1. 2. Mount the distribution media on the desired location (for example, mount -dr /dev/rz4c /CDROM). Change your working directory to the kit location 3. (for example, cd /CDROM/DASS3964310). Issue the 4. setld -l command to load the product onto the system, and follow the installation dialogs (for example, setld -l DASS3964310). Running the IVP Running the IVP Running the IVP During the installation procedure you can run the IVP as part of the installation. If you did not run the IVP at that time or the product does not work correctly, you can run the IVP at any time by issuing the following command: setld -v DASS3964310 Getting Help and Reporting Problems Getting Help and Reporting Problems Getting Help and Reporting Problems If an error occurs while you are using the DAS for Siemens 3964, and you believe the error is the result of a problem associated with the product, take one of the following actions: If you have a basic or DECsupport Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. Device Access Software for Siemens 3964 User Guide 2 2 2- - -5 5 5 Installing the DAS for Siemens 3964 on Your Platform If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). If you purchased the product within the last 90 days and you think the problem is casued by a software error, you can submit an SPR. If you submit an SPR, please 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. 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, relevant data files and so forth. 4. Provide a list of the program. 5. If the program is longer than 50 lines, submit a copy of it on machine-readable media (floppy diskette or magnetic tape). If necessary, also submit a copy of the program library used to build the application. 6. Report only one program per SPR. This will facilitate a faster response. 7. Mail the SPR package to DIGITAL. Experience shows that many SPRs do not contain enough information to duplicate or identify the problem. Concise, complete information helps DIGITAL give timely and accurate service to software problems. If you find an error in the documentation, send an electronic mail message to manufacturing@digital.com. 2 2 2 6 6 6 - - - Device Access Software for Siemens 3964 User Guide Installing the DAS for Siemens 3964 on Your Platform Installation on Windows NT Systems Installation on Windows NT Systems Installation on Windows NT Systems Device Access Software features for Siemens 3964 can only be accessed via BASEstar Open (the DEComni API is not currently available). Preparing for DAS for Siemens 3964 Installation Preparing for DAS for Siemens 3964 Installation Preparing for DAS for Siemens 3964 Installation Before starting the installation procedure, you should complete the preparation requirements outlined in this section. License Registration License Registration License Registration The installation requests a software key. You must enter this code in order to make the DAS for Siemens 3964 Version 3.1 available on your system. For further information about the software key, refer to the DAS for Siemens 3964 Cover Letter. Software Requirements (BASEstar Open Environment) Software Requirements (BASEstar Open Environment) Software Requirements (BASEstar Open Environment) Check that the software products listed in Table 2-3 have been installed on your system. - - - Table Table Table 2 2 2 : Pre-requisite Software for Windows NT : Pre-requisite Software for Windows NT : Pre-requisite Software for Windows NT 3 3 3 Subset Name and Subset Name and Subset Name and Comments Comments Comments Description Description Description BASEstar Open Server Ensure that the BASEstar for Windows NT Version Open Device Connectivity 3.1 has been installed. See the BASEstar Open Server Inst. & Management Guide for your platform for details. Disk Space Requirements Disk Space Requirements Disk Space Requirements The files copied under the installation directory by the installation procedure occupy 48 Kbytes on a Windows NT Intel system and 51 Kbytes on a Windows NT Alpha system. Backing UpYour System Disk Backing UpYour System Disk Backing UpYour System Disk DIGITAL recommends that you back up your system disk before installing any software. For information about how to perform a system disk backup, refer to your Windows NT documentation. Device Access Software for Siemens 3964 User Guide 2 2 2 7 7 7 - - - Installing the DAS for Siemens 3964 on Your Platform Installing the DAS for Siemens 3964 Installing the DAS for Siemens 3964 Installing the DAS for Siemens 3964 To install Device Access Software for Siemens 3964 on a Windows NT system, you must be a member of the Administrators group. To initiate the installation procedure, run the SETUP.EXE file from diskette 1 of the distribution set. The Device Access Software for Siemens 3964 installation procedure allows you to specify a the installation directory. Installing the Device Access Software for Siemens 3964 on your Windows NT system takes about one minute. Files Installed on Your System Files Installed on Your System Files Installed on Your System The directories and files created by the Device Access Software for Siemens 3964 installation proccedure are as follows: \3964\BIN\das3964.dll \3964\INCLUDE\omnii4.h \3964\LIB\3964.fsm \3964\LIB\3964r.fsm \3964\LIB\das3964.lib \3964\relnotes.txt Deinstalling the DAS for Siemens 3964 Deinstalling the DAS for Siemens 3964 Deinstalling the DAS for Siemens 3964 To deinstall the Device Access Software for Siemens 3964, double click on the uninstaller DAS for `` Siemens 3964'' icon in the BASEstar Open Program Manager. Getting Help and Reporting Problems Getting Help and Reporting Problems Getting Help and Reporting Problems If an error occurs while you are using the DAS for Siemens 3964, and you believe the error is the result of a problem associated with the product, take one of the following actions: If you have a basic or DECsupport Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). If you purchased the product within the last 90 days and you think the problem is casued by a software error, you can submit an SPR. 8 8 8 2 2 2 Device Access Software for Siemens 3964 - - - User Guide Installing the DAS for Siemens 3964 on Your Platform If you submit an SPR, please 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. 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, relevant data files and so forth. Provide a list of the program. 4. If the program is longer than 50 lines, submit a 5. copy of it on machine-readable media (floppy diskette or magnetic tape). If necessary, also submit a copy of the program library used to build the application. Report only one program per SPR. This will 6. facilitate a faster response. 7. Mail the SPR package to DIGITAL. Experience shows that many SPRs do not contain enough information to duplicate or identify the problem. Concise, complete information helps DIGITAL give timely and accurate service to software problems. If you find an error in the documentation, send an electronic mail message to manufacturing@digital.com. Device Access Software for Siemens 3964 User Guide 2 2 2- - -9 9 9 Installing the DAS for Siemens 3964 on Your Platform Installation on OpenVMS Systems Installation on OpenVMS Systems Installation on OpenVMS Systems The information that follows is valid for both Alpha and VAX architectures unless otherwise stated. The installation requirements vary depending on whether you are installing the DAS for Siemens 3964 for use via BASEstar Open services or via the DEComni API. Preparing for DAS for Siemens 3964 Installation Preparing for DAS for Siemens 3964 Installation Preparing for DAS for Siemens 3964 Installation Installing the Device Access Software for Siemens 3964 and running the Installation Verification Procedure (IVP) on your OpenVMS system takes approximately 3 minutes. Before starting the installation procedure you should complete the preparation requirements outlined in this section. License Registration License Registration License Registration You must use the License Management Facility (LMF) to register the Device Access Software for Siemens 3964 in accordance with the license agreement signed for your site before you can run either the Installation Verification Procedure (IVP) or the software. License registration information is included in the Product Authorization Key (PAK) that is shipped with the Device Access Software for Siemens 3964. The PAK contains licensing information that should be registered you start the installation. before To register the license, log into the SYSTEM account and set your default to SYS$UPDATE. You can use either of the following two methods to register the license under LMF: Invoke the following procedure and enter the data supplied by the PAK: $ SYS$UPDATE:VMSLICENSE.COM Enter the following command, using the qualifiers that specify the data supplied by the PAK: $ LICENSE REGISTER DAS3964 /qualifier,... If you plan to use the Device Access Software for Siemens 3964 on more than one node of a VAXcluster system, you must load the license on each of the other nodes after you have completed this one. For complete information about using the OpenVMS License Management Facility, refer to the OpenVMS License Management Utility Manual. 10 10 10 - - - 2 2 2 Device Access Software for Siemens 3964 User Guide Installing the DAS for Siemens 3964 on Your Platform Software Requirements (BASEstar Open Environment) Software Requirements (BASEstar Open Environment) Software Requirements (BASEstar Open Environment) Before starting the installation procedure, you should complete the preparation requirements outlined in this section. If you are installing the DAS for Siemens 3964 in the BASEstar Open environment, check that the software products listed in Table 2-4 Table 2-5 and have been installed and are functioning on your system. - - - 2 2 2 Table Table Table 4 4 4: Pre-requisite Software for OpenVMS : Pre-requisite Software for OpenVMS : Pre-requisite Software for OpenVMS (BASEstar Open Environment) (BASEstar Open Environment) (BASEstar Open Environment) Subset Name and Subset Name and Subset Name and Comments Comments Comments Description Description Description BASEstar Open Server Ensure that the BASEstar for OpenVMS Version 3.1 Open Device Connectivity (DEComni, including the DASware RS232 facility) has been installed. See the BASEstar Open Server Inst. & Management Guide for your platform for details. - - - 2 2 2 Table Table Table 5 5 5: Pre-requisite Software for OpenVMS : Pre-requisite Software for OpenVMS : Pre-requisite Software for OpenVMS (DEComni API Environment) (DEComni API Environment) (DEComni API Environment) Subset Name and Subset Name and Subset Name and Comments Comments Comments Description Description Description BASEstar Open Server Ensure that the BASEstar for OpenVMS Version 3.1 Open Device Connectivity (DEComni, including the DASware RS232 facility) has been installed. See the BASEstar Open Server Inst. & Management Guide for your platform for details. If you do not wish to use a direct connection to the device, make sure that the appropriate transport network software indicated in Table 2-6 has been installed and configured. Device Access Software for Siemens 3964 User 2 2 2 Guide 11 11 11 - - - Installing the DAS for Siemens 3964 on Your Platform Table Table Table : Transport Network Software : Transport Network Software : Transport Network Software - - -6 6 6 2 2 2 Subset Name and Subset Name and Subset Name and Comments Comments Comments Description Description Description RS232 LAT (supplied with VMS) Disk Space Requirements Disk Space Requirements Disk Space Requirements The DAS for Siemens 3964 on OpenVMS occupies approximately 500 blocks. Backing UpYour System Disk Backing UpYour System Disk Backing UpYour System Disk DIGITAL recommends that you back up your system disk before installing any software. For information about how to perform a system disk backup, refer to your OpenVMS documentation. Installing the DAS for Siemens 3964 Installing the DAS for Siemens 3964 Installing the DAS for Siemens 3964 This section describes the installation, deinstallation and IVP procedures for the Device Access Software for Siemens 3964 for OpenVMS. Use the following command to install the DAS for Siemens 3964: $ @SYS$UPDATE:VMSINSTALL DAS3964A310 ddcu where ddcu is the installation directory. Files Installed on Your System Files Installed on Your System Files Installed on Your System This section lists directories and files created by the Device Access Software for Siemens 3964. SYS$COMMON:[SYSLIB] AS3964_SHR.EXE OMNI_INTEGRATOR4_DEFS_INCLUDE.H OMNI_INTEGRATOR4_DEFS_INCLUDE.H OMNI_INTEGRATOR4_DEFS_INCLUDE.ADA OMNI_INTEGRATOR4_DEFS_INCLUDE.PAS OMNI_INTEGRATOR4_DEFS_INCLUDE.BAS OMNI_INTEGRATOR4_DEFS_INCLUDE.FOR OMNI_INTEGRATOR4_DEFS_INCLUDE.MAR OMNI_INTEGRATOR4_DEFS_INCLUDE.PLI 2 2 2 12 12 12 - - - Device Access Software for Siemens 3964 User Guide Installing the DAS for Siemens 3964 on Your Platform OMNI_INTEGRATOR4_DEFS_INCLUDE.R32 DAS3964_STARTUP.COM Getting Help and Reporting Problems Getting Help and Reporting Problems Getting Help and Reporting Problems If an error occurs while you are using the DAS for Siemens 3964, and you believe the error is the result of a problem associated with the product, take one of the following actions: If you have a basic or DECsupport Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). If you purchased the product within the last 90 days and you think the problem is casued by a software error, you can submit an SPR. If you submit an SPR, please 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. Demonstrate the problem with specific examples. Reduce the problem to as small a size as possible. 2. 3. Remember to include listings of any command files, include files, relevant data files and so forth. 4. Provide a list of the program. If the program is longer than 50 lines, submit a 5. copy of it on machine-readable media (floppy diskette or magnetic tape). If necessary, also submit a copy of the program library used to build the application. Report only one program per SPR. This will 6. facilitate a faster response. 7. Mail the SPR package to DIGITAL. Experience shows that many SPRs do not contain enough information to duplicate or identify the problem. Concise, complete information helps DIGITAL give timely and accurate service to software problems. Device Access Software for Siemens 3964 User Guide 2 2 2 - - -13 13 13 Installing the DAS for Siemens 3964 on Your Platform If you find an error in the documentation, send an electronic mail message to manufacturing@digital.com. 14 14 14 - - - Device Access Software for Siemens 3964 2 2 2 User Guide PART I PART I PART I Using BASEstar Open to Communicate With Siemens 3964 Using BASEstar Open to Communicate With Siemens 3964 Using BASEstar Open to Communicate With Siemens 3964 Devices Devices Devices This part describes how to access Siemens 3964 devices via BASEstar Open services, and how to configure BASEstar Open for use with the DAS for Siemens 3964. It also provides code examples that you can run in the BASEstar Open environment. The Command Language Interface (CLI) is used to create and operate the required BASEstar Open objects. However, you could use the Application Programming Interface (API), or the Graphical Configuration Utility (GCU) to perform the same tasks. 3 3 3 Overview Overview Overview This chapter describes the BASEstar Open environment components involved when you access Siemens 3964 devices via BASEstar Open services. It also provides an overview of the operations that you can perform using the features provided by the DAS for Siemens 3964: Exchanging data messages with a Siemens 3964 device using the 3964[R] protocol. Reading and writing the memory of a Siemens 3964 device using the 3964[R]_RK512 protocol. The chapter also discusses how a system equipped with BASEstar Open can emulate Siemens 3964 devices that accept and fulfill requests received from remote devices via the Siemens 3964[R]_RK512 protocol. Device Access Software for Siemens 3964 User Guide - - - 3 3 3 1 1 1 Overview BASEstar Open Environment Components BASEstar Open Environment Components BASEstar Open Environment Components Figure 3-1 shows the environment components involved when you exchange data with Siemens 3964 devices. Figure Figure Figure - - -1 1 1 3 3 3 : BASEstar Open Environment Components : BASEstar Open Environment Components : BASEstar Open Environment Components Data Services Data Services Data Services BASEstar Open users use Device_Data_Points to read and write memory locations of a Siemens 3964 device. When a user writes the value of a Device_Data_Point, BASEstar Open Device Services sends a message to the appropriate Siemens 3964 device. Vice versa, BASEstar Open updates the value of a Device_Data_Point each time it receives an unsolicited message from a Siemens 3964 device. Each Device_Data_Point is linked to a Device Services variable which, in turn, is associated with the VMD definition that models the target device. 3 3 3 Device Access Software for Siemens 3964 User Guide 2 2 2 - - - Overview Device Services Device Services Device Services BASEstar Open Device Services provides a unique set of operations to BASEstar Open users for device- independent access to any type of device or network. This device-independent approach to device connectivity is possible because Device Services models a device as a MMS Virtual Manufacturing Device (VMD). Each Device Services VMD corresponds to a Siemens 3964 device. A variable associated with this VMD corresponds to a memory location on the same device. DEComni API DEComni API DEComni API The DEComni API is the engine that provides BASEstar Open Device Services with MMS functions. DEComni API also provides a standardized means of adding new DAS modules to the BASEstar Open environment. The Omni Directory Services (ODS) database is the DEComni API component that allows you to define the information required for addressing Siemens 3964 devices connected via an RS232 port or terminal server. DIGITAL DAS for Siemens 3964 DIGITAL DAS for Siemens 3964 DIGITAL DAS for Siemens 3964 The DIGITAL DAS for Siemens 3964 is a BASEstar Open device connectivity module that implements the Siemens 3964[R] and 3964[R]_RK512 protocols. Device Access Software for Siemens 3964 User Guide 3 3 3- - -3 3 3 Overview Exchanging Data Messages With a Siemens 3964 Device (3964[R] Exchanging Data Messages With a Siemens 3964 Device (3964[R] Exchanging Data Messages With a Siemens 3964 Device (3964[R] Protocol) Protocol) Protocol) The DAS for Siemens 3964 allows a BASEstar Open user to communicate with a Siemens 3964 device according to the 3964[R] protocol. Figure 3-2 shows the BASEstar Open objects and the commands a BASEstar Open user must use to receive data messages from (and send data messages to) a remote Siemens 3964 device. Figure Figure Figure : BASEstar Open Objects and Operations : BASEstar Open Objects and Operations : BASEstar Open Objects and Operations - - -2 2 2 3 3 3 (3964[R] Protocol) (3964[R] Protocol) (3964[R] Protocol) Sending Data Sending Data Sending Data A BASEstar Open user must issue a PUT_VALUE command on a Device_Data_Point to send a data message to a remote Siemens 3964 device. The Device_Data_Point must be linked to a Device Services variable which is, in turn, associated with a VMD defined for that device. Several variables can be associated with the same VMD, and a user can use each of the Device_Data_Points linked to these variables to send data messages of different lengths. BASEstar Open sends the remote device a number of characters from the user buffer equal to the size in bytes of the datatype that has been associated with the variable used for the send operation. 3 3 3 Device Access Software for Siemens 3964 User Guide - - -4 4 4 Overview The PUT_VALUE command returns control to the application as soon as BASEstar Open has sent the data through the local port successfully. Receiving Data Receiving Data Receiving Data A BASEstar Open user must issue a GET_VALUE command on a Device_Data_Point to obtain from BASEstar Open the value of a data message coming from a remote Siemens 3964 device. The Device_Data_Point must have been configured for receive operations, and must be linked to the "reception variable" associated with the VMD that models the device. BASEstar Open always uses the reception variable to return the data received from the Siemens 3964 device. The "reception variable" is the Device Services first Named_Variable that has been created for the VMD. If no Named_Variable has been defined, the first Unnamed_Variable is used. If no variable is associated with the remote VMD, any data received from the device are lost. The GET VALUE command returns to the user the cached value of the Device_Data_Point itself; that is, there is no interaction with the DAS nor with the device. BASEstar Open updates the value of the Device_Data_Point regardless of the receive operations performed by the user. When receiving a message from the device, BASEstar Open generates an internal Inforeport that causes the unsolicited updating of the cached value of the Device_Data_Point that is linked to the Device Services "reception variable". BASEstar Open interprets the data received from the device in one data message according to the datatype associated with the "reception variable". Note that if an insufficient number of bytes is received, the value returned in the user buffer is unpredictable; if, instead, the number of the received bytes exceeds that required to meet the datatype, the exceeding bytes are lost. Device Access Software for Siemens 3964 User Guide - - -5 5 5 3 3 3 Overview Accessing the Memory of a Siemens 3964 Device (3964[R]_RK512 Accessing the Memory of a Siemens 3964 Device (3964[R]_RK512 Accessing the Memory of a Siemens 3964 Device (3964[R]_RK512 Protocol) Protocol) Protocol) A BASEstar Open user gets (or puts) the value of a Device_Data_Point to read data from (or write data to) a physical memory location of a Siemens 3964 device. As shown in Figure 3-3, this Device_Data_Point must be linked to an Unnamed_Variable associated with a VMD that models the device. A GET_VALUE command reads data from the device memory, and returns in the user buffer a number of characters that is equal to the size of the BASEstar Open DataType associated with the variable used for read operations. A similar consideration applies to a PUT_VALUE command. Figure Figure Figure 3 3 3: Using BASEstar Open to Access the Memory : Using BASEstar Open to Access the Memory : Using BASEstar Open to Access the Memory - - - 3 3 3 of a Siemens 3964 Device of a Siemens 3964 Device of a Siemens 3964 Device To obtain a BASEstar Open configuration that is appropriate for your needs, you must consider the requirements of your overall application. Figure 3-3 illustrates an example in which BASEstar Open operations are synchronous with user's actions; in fact: Each time the user issues a PUT_VALUE command, BASEstar Open immediately updates the device memory. Each time the user issues a GET_VALUE command, BASEstar Open immediately reads the device memory. However, you can configure BASEstar Open for asynchronous operations by means of a Polling_Set. In this case, BASEstar Open automatically reads the value of the device memory, and updates the value of 3 3 3 6 6 6 Device Access Software for Siemens 3964 User Guide - - - Overview the Device_Data_Point asynchronously with respect to the user's actions. Device Access Software for Siemens 3964 User Guide 3 3 3- - -7 7 7 Overview Emulating a Siemens 3964 Device (3964[R]_RK512 Protocol) Emulating a Siemens 3964 Device (3964[R]_RK512 Protocol) Emulating a Siemens 3964 Device (3964[R]_RK512 Protocol) Figure 3-4 shows how BASEstar Open emulates a Siemens 3964 device via a local VMD. When emulating a Siemens 3964 device, BASEstar Open acts as a server; that is, it accepts and fulfills write and read requests received from a remote Siemens 3964 device or a BASEstar Open user. Figure Figure Figure : Using BASEstar Open to Emulate a Siemens : Using BASEstar Open to Emulate a Siemens : Using BASEstar Open to Emulate a Siemens - - -4 4 4 3 3 3 3964 Device 3964 Device 3964 Device To direct BASEstar Open to act as server you must create a local VMD object for each Siemens 3964 device you want to emulate, and you must associate a Device Services Unnamed_Variable to the VMD for each memory block to be emulated. BASEstar Open users can exchange data messages with emulated Siemens 3964 devices as described in the section of this chapter entitled Exchanging Data Messages With a Siemens 3964 Device (3964[R] Protocol). Datatypes and Memory Block Sizes Datatypes and Memory Block Sizes Datatypes and Memory Block Sizes A GET_VALUE command returns in the user buffer a number of characters that is equal to the size of the BASEstar Open datatype associated with the variable used in the read operation. The size (in bytes) of this data type must therefore be equal to the size (in bytes) of the data that are contained in a data block (represented by the variable). A similar consideration applies to the PUT_VALUE command. 3 3 3 8 8 8 - - - Device Access Software for Siemens 3964 User Guide Overview In order to simplify the calculation of the sizes of BASEstar Open datatypes, Appendix B provides the sizes of the basic BASEstar Open datatypes. Device Access Software for Siemens 3964 User Guide 3 3 3 9 9 9 - - - 4 4 4 Configuring BASEstar Open Configuring BASEstar Open Configuring BASEstar Open This chapter describes how you must configure BASEstar Open in order to allow users to access a Siemens 3964 device. To configure BASEstar Open you must: Register the appropriate entries in the ODS database. Create the required Application Services Activity and Program objects. Create the required Device Services Protocol_Profile, VMD and Variable objects. Create the required Device_Data_Point objects. _______________________ _______________________ _______________________Note Note Note_____________________ _____________________ _____________________ For an explanation of the BASEstar Open object attributes whose values are not specified in this chapter, refer to the BASEstar Open Command Language Interface and the BASEstar Open Reference Guide. ________________________________ ________________________________ ________________________________________________ ________________ ________________ Device Access Software for Siemens 3964 User Guide 1 1 1 4 4 4- - - Configuring BASEstar Open Registering ODS Entries Registering ODS Entries Registering ODS Entries For each Siemens 3964 device you must create an ODS entry which specifies Siemens 3964 protocol-specific information. See Appendix A for details. Creating Application Services Objects Creating Application Services Objects Creating Application Services Objects You can use the DATADEV server or separate Device and Data servers. The DATADEV server makes both Data and Device Services servers available in a single process, thus simplifying configuration operations, optimizing performance, and allowing the same Device_Data_Point to be used for both send and receive operations. ______________________ ______________________ ______________________ _____________________ _____________________ _____________________ Note Note Note The DATADEV server is used throughout this manual, therefore you should modify the information and examples provided in this chapter if you want to use two separate Device and Data Services servers (for example, if your BASEstar Open version does not support DATADEV servers). ________________________________ ________________________________ ________________________________________________ ________________ ________________ See also Chapter 5 for examples showing the commands used to create the required Program and Activity objects. For further details, refer to the BASEstar Open Command Language Interface and to the BASEstar Open Reference Guide. Creating Device Services Objects Creating Device Services Objects Creating Device Services Objects You must create the following Device Services objects in the order listed below: 1.Protocol_Profile 2.VMD 3.Variables Creating Protocol_Profiles Creating Protocol_Profiles Creating Protocol_Profiles Device Services uses Protocol_Profiles to associate a VMD with the appropriate DAS. You must create one Protocol_Profile for each Siemens 3964 protocol, and you can use it for all the VMDs that are associated with that protocol. Table 4-1 lists the Protocol_Profile attributes whose values are specific to the Siemens 3964 protocols. 4 4 4 - - - Device Access Software for Siemens 3964 User Guide 2 2 2 Configuring BASEstar Open Table Table Table 4 4 4- - -1 1 1: Protocol_Profile Attributes : Protocol_Profile Attributes : Protocol_Profile Attributes Attribute Attribute Attribute Description and Values Description and Values Description and Values Name Name Name - The identifier of the DAS to be used. APPLPROFID Possible values are: "31" for the Siemens 3964 protocol "32" for the Siemens 3964R protocol "33" for the Siemens 3964_RK512 protocol "34" for the Siemens 3964R_RK512 protocol - The maximum length of the data exchanged MAXPDUSIZE with the Siemens 3964 device. For the 3964[R] protocol, there is no limit in the size of the message exchanged. You can specify any value, provided it is supported by DEComni API. For the 3964[R] _RK512 protocol, there is no limit in the size of the message exchanged between DEComni API applications and Siemens 3964 devices, but the message is segmented for transmission over the communication line. This attribute must specify the segment size, which must be less than, or equal to 138 (including 10 bytes for the header). Example 4 shows how to create the 1 - Protocol_Profiles for all the supported protocols. Example Example Example - - - : Creating Device Services : Creating Device Services : Creating Device Services 1 1 1 4 4 4 Protocol_Profiles Protocol_Profiles Protocol_Profiles BSTR> CREATE PROTOCOL_PROFILE PP_3964 -APPLPROFID 31\ -MAXPDUSIZE 1024 -LOG BSTR> CREATE PROTOCOL_PROFILE PP_3964R -APPLPROFID 32\ -MAXPDUSIZE 1024 -LOG BSTR> CREATE PROTOCOL_PROFILE PP_3964_RK512 - APPLPROFID 33\ -MAXPDUSIZE 138 -LOG BSTR> CREATE PROTOCOL_PROFILE PP_3964R_RK512 - APPLPROFID 34\ -MAXPDUSIZE 138 -LOG Creating VMDs Creating VMDs Creating VMDs A Device Services VMD models a Siemens 3964 device. Table 4-2 lists the mandatory attributes that you Device Access Software for Siemens 3964 User Guide - - - 4 4 4 3 3 3 Configuring BASEstar Open must specify for a correct definition of a Siemens 3964 VMD for any of the supported protocols. Table Table Table 2 2 2: VMD Attributes : VMD Attributes : VMD Attributes 4 4 4- - - Attribute Name Attribute Name Attribute Name Description and Values Description and Values Description and Values - When creating a rem