Industrial IT. Fieldbus Basic PROFIBUS DTM / PROFIBUS DTM Builder Version 4.1. Configuration

Transcription

1 Industrial IT Fieldbus Basic PROFIBUS DTM / PROFIBUS DTM Builder Version 4.1 Configuration

2

3 Industrial IT Fieldbus Basic PROFIBUS DTM / PROFIBUS DTM Builder Version 4.1 Configuration

4 NOTICE The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document. In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. Copyright ABB All rights reserved. TRADEMARKS Release: May 2005 Document number: 3BDD011788R4101 Registrations and trademarks used in this document include: Windows Industrial IT Registered trademark of the Microsoft Corporation Trademark of ABB

5 TABLE OF CONTENTS About This Book General...9 Use of Caution, Information, and Tip Icons...9 Document Conventions...10 Terminology...11 Relevant Documentation...13 Section 1 - Introduction Product Overview...15 Product Scope...15 New This Release...16 Installation...16 Prerequisites and Requirements...17 Software Environment...17 Registration...17 Ordering and registering the license key...18 Transferring the software to another computer...19 Intended User...19 Notes for use...20 Section 2 - Application PROFIBUS Protocol Description...21 PROFIBUS-DP System Configuration...23 Slave Data...23 Device Master Data...24 PROFIBUS-DP States BDD011788R4101 5

6 Table of Contents Configuration...25 Parameterization...26 Cyclic data exchange...26 Acyclic data exchange...26 Data Storage...26 User Interfaces...27 Frame Application...27 User Roles...28 Buttons...29 Input/Output Boxes...30 Status Bar...31 Licensing...32 Graphical User Interfaces of the DTM...34 Default View...34 About...35 Administration...36 Device Types...36 Device Data...39 DTM Data...39 Identification...40 Information...40 Definition...42 Bus...44 Configuration...47 Miscellaneous...48 User Parameters...51 DPV Module...58 PROFIBUS Application Editor...61 Application Explore...63 Toolbox...66 Application Properties BDD011788R4101

7 Table of Contents Application Layout...74 Invoke User Defined Applications...75 User defined GUI...75 Online Functions...78 Observe...78 Online Parameterization...81 Online Compare...83 Non-GUI Applications...85 Upload...85 Download...85 Online Compare...85 OPC Access...86 Print actual data...86 Audit Trail...86 Export/Import of data...86 Placeholder...87 How to work with the Placeholder...87 Templates and Profiles...88 Profiles...88 Templates...88 Appendix A - Data Types Simple...91 INDEX 3BDD011788R4101 7

8 Table of Contents 8 3BDD011788R4101

9 About This Book General This book contains a detailed description of how to use the Basic PROFIBUS DTM/PROFIBUS DTM Builder. For the latest information, please also refer to the corresponding Release Notes. Use of Caution, Information, and Tip Icons This publication includes Caution, and Information where appropriate to point out safety-related or other important information. It also includes Tips to point out useful hints to the reader. The corresponding symbols should be interpreted as follows: The caution icon indicates important information or a warning related to the concept discussed in the text. It may indicate the presence of a hazard, which could result in software corruption or damage to equipment/property. The information icon draws the reader s attention to pertinent facts and conditions. The tip icon provides advice about how, for example, to design your project or use a certain function Although Caution hazards are associated with damage to equipment or property, it should be understood that operation of damaged equipment could, under certain operational conditions, result in downgraded process performance leading to personal injury or death. It is therefore essential to comply fully with all Warning and Caution notices. 3BDD011788R4101 9

10 Document Conventions About This Book Document Conventions The following conventions are used for the presentation of material: The words in names of screen elements (for example, the title in the title bar of a window, the label for a dialog box field) are written with initial capital letters. Capital letters are used for the name of a keyboard key if it is labeled on the keyboard. For example, press the ENTER key. Lower case letters are used for the name of a keyboard key that is not labeled on the keyboard. For example, the space bar, comma key, and so on. Press CTRL+C indicates that you must hold down the CTRL key while pressing the C key (to copy a selected object in this case). Press ESC E C indicates that you must press and release each key in sequence (to copy a selected object in this case). The names of push buttons and toggle buttons appear in brackets and bold type. For example, click [OK]. The names of menus and menu items appear in bold type. For example, the File menu. The following convention is used for menu operations: MenuName > MenuItem > CascadedMenuItem. For example: select File > New > Type. The Start menu name always refers to the Start menu on the Windows taskbar. System prompts/messages appear in the Courier font and user responses/inputs appear in Courier bold font. For example, if you enter a value out of range, the following message appears: Entered value is not valid. The value must be 0 to 30. You may be told to enter the string TIC132 in a field. The string is shown as follows in the procedure: TIC132 Variables appear in lower case letters. sequence name 10 3BDD011788R4101

11 About This Book Terminology Terminology The following is a list of terms associated with the Basic PROFIBUS DTM/PROFIBUS DTM Builder that one should be familiar with. The list contains terms and abbreviations that are unique to ABB or have a usage or definition that is different from standard industry usage. Term/Acronym Basic PROFIBUS DTM Device Type Manager (DTM) Device Description Language (DDL) Frame Application (FA) Fieldbus Builder (FBB) Description DTM for PROFIBUS devices, additionally serving as a runtime environment for device specific DTMs, that have been built with the PROFIBUS DTM Builder Software component (device driver) for configuring, diagnosing, forcing, displaying the measured variables, etc. of a field device. It is familiar with the way the device works and supplies device specific documentation. Interpretable language for the formal description of device parameters Frame application (run time environment) in accordance with the FDT specification for operating DTMs ABB aspect system for fieldbus and DTM management, implementing a frame application according to specification FDT 1.2 Field Device Tool (FDT) The FDT concept describes the interface between a frame application and the device-specific software (DTM = Device Type Manager) of the device manufacturer. It enables devices produced by different manufacturers and different fieldbuses to be integrated in a single system. Currently supporting fieldbus protocols for PROFIBUS and HART. Graphical User Interface (GUI) Industrial IT Graphical interface for user interactions Industrial IT is ABB s solution for business processes. It allows seamless integration of systems for plant automation, plant optimisation and common business processes at run time 3BDD011788R

12 Terminology About This Book Term/Acronym Industrial IT System Process Portal A (PPA) PROFIBUS DTM Builder System Application Description A computer system that implements (part of) the Industrial IT vision. Process Portal A is an example of such a system. Industrial IT System Product containing functionality for efficient control and supervision of an automated process. Key functions are presentation of graphics, process dialogs and presentation of alarms and trends.platform for the integration of different aspect systems e.g. Fieldbus Builder PROFIBUS/HART Software product consisting of an DP V1 editor to define device specific PROFIBUS DTMs, to be executed by the Basic PROFIBUS DTM. A software package that provides functionality in the Industrial IT System. System applications cooperate according to rules defined by the Industrial IT architecture, using mechanism provided by the Process Portal A. They are normally bundled into System Products. To participate in Aspect Object operations, and thus be an integrated part of an Industrial IT system, a system application must present itself as an aspect system. When there is no risk for confusion with user application, the term application may be used instead of system application. 12 3BDD011788R4101

13 About This Book Relevant Documentation Relevant Documentation The table below contains a list of relevant documentation. Category Title 800xA Fieldbus DTM Industrial IT, 800xA - System, Installation 3BSE Industrial IT, 800xA - Device Management, PROFIBUS, Configuration 3BDD Industrial IT, 800xA - Device Management, PROFIBUS, Release Notes 3BDD Industrial IT, Fieldbus Basic PROFIBUS DTM / PROFIBUS DTM Builder, Installation Guide 3BDD Description The document describes the installation procedure The document describes the basic features and how to configure the individual software components This document contains the latest information The document describes the installation procedure for the DTM 3BDD011788R

14 Relevant Documentation About This Book 14 3BDD011788R4101

15 Section 1 Introduction Product Overview The FDT concept describes the interface between a frame application and the device-specific software (DTM = Device Type Manager) of the device manufacturer. It enables devices produced by different manufacturers and for different fieldbuses to be integrated in a single system. The DTM is a software component, which is usually supplied by the manufacturer together with the intelligent field device. The DTM is familiar with the way the field device works (plausibility), offers graphical user dialogs, manages device configuration and diagnostics, and supplies the device-specific documentation. ABB provides a Basic DTM ("Basic PROFIBUS DTM") for PROFIBUS field devices without a dedicated DTM. Furthermore with the expansion of the Basic PROFIBUS DTM to the PROFIBUS DTM Builder dedicated DTMs can be developed using the Basic PROFIBUS DTM supported applications. The Basic PROFIBUS DTM/PROFIBUS DTM Builder enables the field devices to be operated in a frame application conforming to FDT 1.2. Product Scope The Basic PROFIBUS DTM/PROFIBUS DTM Builder is suitable for executing various tasks, also referred to as applications in the following description. Most applications have a graphical user interface for data visualization and data entry. The last four applications in the list do not have a graphical interface. 3BDD011788R

16 New This Release Section 1 Introduction New This Release The application call takes place by a menu offered by the DTM or the frame application. About DTM Default View Identification Configuration Online Parameterization Observe Download Upload Verify Online Compare Application Editor (Only available with DTM Builder) Administration Registration Table 1. Versions Version Description 3.1 First version 4.0 New features and corrections 4.1 corrections Installation The installation of the Basic PROFIBUS DTM/PROFIBUS DTM Builder is described in the Basic PROFIBUS DTM/PROFIBUS DTM Builder, Installation Guide 3BDD BDD011788R4101

17 Section 1 Introduction Prerequisites and Requirements Prerequisites and Requirements Software Environment The DTM (software) requires a frame application conforming to FDT 1.2 with Addendum and one of the following operating systems: Windows 2000 with Service Pack > 2 Windows XP with Service Pack > 1 Windows 2003 Server Also required is Internet Explorer > 5.5 with XML 3.0 and the ABB Shared Components version > 3.1. Registration The Basic PROFIBUS DTM requires a license key during the installation. This license will be delivered together with the ordered software. The license of The PROFIBUS Device Integration includes the license for the Basic PROFIBUS DTM. A separate license key is required for the PROFIBUS DTM Builder. This is associated with the one workstation computer on which the software is to be installed and operated. The license for the Basic HART DTM shall be entered from the user during installation. Without this license key the installation can not proceed successful. The PROFIBUS DTM Builder can be only enabled with a separate license key. Therefore a demo mode functionality is not available in this version. When you purchase the product you will receive a license certificate containing an individual license number as well as a request form. Please order and register the license key as described in the following text. 3BDD011788R

18 Registration Section 1 Introduction Ordering and registering the license key 1. Install the software on the workstation computer on which it will be used. 2. Start the application and open the "Registration" dialog box. 3. Enter the hardware identifier indicated for the workstation computer on the request form. 4. Send the form to the ABB order box address (Germany). The license key will then be sent to you in the required format. Figure 1. Registering the license key 5. Next, press the [Browse] button to import the license key into the "Registration" dialog box. Once the file has been read in and the data verified as correct, the message "Valid license key present" will appear. The product and all its functions can now be accessed on this workstation without being subject to a time limit. 18 3BDD011788R4101

19 Section 1 Introduction Intended User If the message "Invalid license key present" appears, check whether the license key is for a different product for a different workstation or for a workstation with different hardware resources, e.g. Ethernet interface card. Intended User Transferring the software to another computer If software that has already been registered on one computer is to be transferred to another computer or the Ethernet interface card has to be replaced, the registration process must be repeated. 1. To do this, send the following information to your local ABB representative: License number on the certificate New hardware ID Delivery address ( address or postal address) Reason for repeat registration 2. You will receive a new license key, which can be imported as described above in order to activate the product on the new workstation computer. This configuration guide is designed for application engineers and commissioning engineers. It explains how to build device-specific DTMs using the PROFIBUS DTM Builder. Those using this manual should be familiar with the basic method of operation of the PROFIBUS protocol. 3BDD011788R

20 Notes for use Section 1 Introduction Notes for use The Basic PROFIBUS DTM/PROFIBUS DTM Builder supports all UNICODE characters, except the following: & < > " ' \t \r \n These characters shall not be used in any graphical user interface (GUI). REAL values use "." as decimal separator, independent from the language settings. The decimal seperator, is not supported. 20 3BDD011788R4101

21 Section 2 Application PROFIBUS Protocol Description PROFIBUS is a fieldbus standard for applications in the manufacturing industry, process automation and building automation. PROFIBUS communication is defined in the standard EN This standard is supplemented by technical guidelines published by PROFIBUS International (PI). Information about PROFIBUS International can be found on the web page The PROFIBUS family consists of three compatible versions: 1. PROFIBUS-FMS This version is the general solution for communication tasks at system level. PROFIBUS FMS services open up a wide range of applications and provide a high level of flexibility. 2. PROFIBUS-DP This version is optimized for high speed and simple connection of devices. This PROFIBUS version is specially designed for communication between programmable controllers and a distributed I/O level. The PROFIBUS-DP protocol supports the extension of the PROFIBUS-DP V1 protocol definition. The PROFIBUS-DP V1 extensions are compatible with the basic PROFIBUS-DP. The use of basic PROFIBUS-DP and PROFIBUS-DP V1 devices is thus possible on the same bus. 3. PROFIBUS-PA This version is specially designed for process automation. PROFIBUS-PA allows sensors and actors to be connected to the same bus, even in security areas. PROFIBUS-PA uses the PROFIBUS-DP protocol with PROFIBUS-DP V1 extensions. 3BDD011788R

22 Section 2 Application Only the bus physics differ for the two versions. PROFIBUS-PA uses bus physics in accordance with IEC , where communication and the power supply take place via the common bus. PROFIBUS-PA networks can be connected to PROFIBUS-DP networks via bus converters like ABB s PROFIBUS DP/PA Linking Device LD 800P. 22 3BDD011788R4101

23 Section 2 Application PROFIBUS-DP System Configuration PROFIBUS-DP System Configuration All three PROFIBUS versions (FMS, DP and PA) use a compatible bus protocol. The communication of I/O data with the connected devices (slaves) takes place via cyclic data exchange. Each PROFIBUS-DP system can contain the following three different types of device: PROFIBUS-DP master class 1 (DPM1) is the central controller, which exchanges information with the slaves in a defined cycle. PROFIBUS-DP master class 2 (DPM2) are programming units or operator panels. They are used during commissioning to configure the PROFIBUS-DP system and for monitoring tasks. PROFIBUS-DP slave is a peripheral device. The extent of the I/O data depends on the type of slave. A maximum of 244 bytes of input data and 244 bytes of output data are possible per slave. The I/O data is transferred cyclically. A slave can also be modular, i.e. contain modules. Slave Data Different information is required to configure a PROFIBUS-DP slave on the PROFIBUS. The I/O data specify which values are to be exchanged cyclically between the master and the slave. The I/O data is structured using the modules connected to the PROFIBUS slave. The structure of the I/O data is specified by the vendor. The standard parameters include firstly the bus parameters which are defined in the device master data. Secondly, they include parameters, which define the modularity and the functional capabilities of the slave. 3BDD011788R

24 Device Master Data Section 2 Application User parameters are specified for each device type. They are used to parameterize the connected PROFIBUS devices. User parameters are documented in the manuals of the respective device vendors or are included in the device master data for more recent device versions. The module set is configured using the modules connected to the PROFIBUS slave. Diagnostic data shows the current state of the slave and the modules. It is defined separately by the PROFIBUS for the slave, each individual module and each channel. In addition, vendor-specific diagnostic data may exist for the slave and the modules. PROFIBUS-DP V1 parameters are used to configure PROFIBUS devices. PROFIBUS-DP V1 parameters are documented in the manuals of the respective device vendors or are included in the device master data for more recent device versions. These can also be imported (DTM Builder License required) via XML files if available. The current version of this DTM supports all the above data except the diagnostic data. Device Master Data PROFIBUS devices have different performance specifications and functional capabilities (for example, the number of I/O signals and items of diagnostic data) or possible bus parameters such as transfer rate and monitoring time. These parameters are very individual for each device type and vendor. The parameters are usually documented in the manuals of the device vendor. The characteristic features are specified in the device master data. The device master data file is made available by the vendor. This file allows DTM to read the device details of any PROFIBUS-DP slave and thus to create an object with which the PROFIBUS system can be configured. The device master data is divided into various areas: General data: This area contains the vendor and model name, hardware version and software version, transfer rate, etc. 24 3BDD011788R4101

25 Section 2 Application PROFIBUS-DP States PROFIBUS-DP master-related data: This area contains all data, which are only used for the PROFIBUS-DP master. This area does not exist for PROFIBUS-DP slaves. PROFIBUS-DP slave-related data: This area contains data, which relates to the slave (for example, parameters, number and type of modules, specification of the diagnosis, etc.). PROFIBUS-DP States The system behavior is mainly determined by the operating state of the PROFIBUS- DP master class 1 (DPM1). A distinction is made between three main states: Stop: In this state, no data exchange takes place between the DPM1 and the PROFIBUS-DP slaves. Clear: In this state, the DPM1 reads the input information of the PROFIBUS-DP slaves and keeps the outputs in fail-safe status. Operate: In this state, data exchange takes place. In cyclic data communication, the DPM1 reads the inputs of the PROFIBUS-DP slaves and writes the outputs to the PROFIBUS-DP slaves. The data exchange between PROFIBUS-DP master class 1 (DPM1) and the assigned PROFIBUS-DP slaves are structured by the DPM1 in a defined order. During the configuration of the PROFIBUS, the assignment of a PROFIBUS-DP slave to a DPM1 is specified. The structure of the data exchange between the DPM1 and the PROFIBUS-DP slave is in three phases. Configuration During the configuration phase, each PROFIBUS-DP slave receives its configuration transferred from the DPM1. The PROFIBUS-DP slave compares the configuration received with its own configuration data. Only if the configuration received matches the configuration data of the PROFIBUS-DP slave, is the PROFIBUS-DP slave accepted into the parameterization phase. 3BDD011788R

26 Parameterization Section 2 Application Therefore, the device type, format and length information and the number of inputs and outputs must tally with the current configuration. The configuration of the device is done in offline mode. Parameterization In the parameterization phase, the PROFIBUS-DP slave receives the vendor-specific parameterization from the DPM1. The content of the vendor-specific parameterization is not standardized and is transferred in a non-structured data block. In addition, the user can start the transfer of the vendor-specific parameterization at any time. There are two phases of parameterization offline or online. In mode offline parameterization, a set of default parameter is configured for the device and later downloaded into the device. Then in the mode online parameterization the final data tuning is done in Online mode for the device. Cyclic data exchange The DPM1 communicates data cyclically with the assigned PROFIBUS-DP slaves. For this DPV0 communication services are used. Acyclic data exchange The DTM communicates data acyclic with the PROFIBUS-DP device. For the socalled DPV1 communication DPV1 services are used. The DPV1 service parameters for the DTM are device specific and their actual values need to be downloaded to the device separately or set in Online Parameterization mode. Data Storage The data (parameters) is only available temporarily in the DTM for processing. When a user interface is closed or data is buffered, the DTM saves the data permanently. In offline mode, data is saved to the workstation computer s database as instance data. In online mode, data is saved first to the field device and then to the database. However, the DTM will only update the data in the database if the field device has 26 3BDD011788R4101

27 Section 2 Application User Interfaces accepted the data. It is always possible that, for technical reasons, a device may not be able to apply the value in the exact format in which it was entered and will therefore apply a value very similar to that entered. User Interfaces Most DTM applications have a graphical user interface for displaying variables, input/output parameter values or writing to the device. Certain applications (download, upload, online compare) do not require a graphical user interface. They are controlled exclusively by the frame application (the DTM works in the background). The user interface comprises a header, which is provided by the frame application. If possible, the header should contain the process point, the device name and the active application. The DTM adds the application-specific area in the middle and two footer lines. The footer contains the standard buttons and a status bar. The images (screenshots) in this document were created on a workstation with standard Windows color settings. Any other settings will result in a different image or, in extreme cases, may distort information so that it can no longer be seen on the screen. Frame Application The DTM informs the frame application about the possible applications. The frame application usually provides a pull-down menu for selecting an application. Depending on the user s rights or the operating state (online/offline), some applications may not be available for selection. The title bar and toolbar shown in the examples should be made available by a frame application. They provide assistance when working with several DTMs or applications in parallel. More detailed information about the selection and presentation of the DTM can be found in the instruction manual for the frame application. 3BDD011788R

28 User Roles Section 2 Application User Roles The DTM checks the user rights when an application starts up. Certain users may even be barred from using some applications. If access to an application is permitted, a distinction is made between restricted access (read-only) and full access (read and write) to its functions:. Table 2. User roles Application User Roles Observer Operator Maintenance Planning Engineer Identification R R R/W R/W Configuration -/- R R R/W Online- Parameterization -/- R R/W R/W Observation R R R R Upload -/- -/- -/- R/W Download -/- -/- -/- R/W Online-Compare R R R R Application Editor -/ -/ R/W R/W User Specified GUI R R R/W R/W Administration R R R/W R/W Registration R R R/W R/W -/- = The user interface is not available for selection R = Data output only (read) R/W = Data input (write) and output (read) If in addition to the roles above, you have administrator or OEM service rights, the role of an observer will grant you unrestricted access to all applications. 28 3BDD011788R4101

29 Section 2 Application Buttons Buttons The following buttons are not application-specific and always have the same function. OK Press the [OK] button to save all data and close the graphical interface. The DTM will then save the data for that application to the database and/or device. Cancel If [Cancel] is pressed, the DTM will reject all data input (since the last time data was applied) and close the interface. Apply Press the [Apply] button to apply the numbers/text input and menu selections made. The DTM will save all modifications made since the last time data was applied. The interface remains open. Help Press the [Help] button to access the online help for an application. The application-specific buttons are described in the section relating to each application. 3BDD011788R

30 Input/Output Boxes Section 2 Application Input/Output Boxes The input/output boxes are used to display and enter data (parameter values). Depending on the meaning of the parameter, numerical values or character strings can be entered. In some cases, these values must be selected from a list containing a fixed number of default entries. Input and output boxes are identified by means of the background brightness. The DTM highlights the fields containing modified data. Pressing the [Apply], [OK] or [Cancel] buttons and performing a save prompts the DTM to remove the highlighting. Output box Input box When data is entered into an input box, the DTM checks the data format, value ranges, etc. The data plausibility check can only be carried out once all data has been entered. The DTM carries out the plausibility check once the [Apply] or [OK] button has been pressed. Entries that conflict with other entries on this user interface are identified accordingly in the appropriate fields. They must be corrected before the data can be applied. Incorrect entries are displayed in red color. 30 3BDD011788R4101

31 Section 2 Application Status Bar Status Bar The status bar at the bottom of the user interface comprises a total of three fields. The left-hand field provides the following information: Data locked Messages Data locked Start communication Data transmission... DTM abort Meaning Another user has already started an application for this device and has reserved the data record. Data can only be entered once the user has quit the application. The DTM tries to establish communication with the field device A request has been sent and the DTM is waiting for a reply from the field device Abort current communication with the field device The current user name and the user role will be displayed in the right-hand field. The field in the centre of the bar contains a round circle (referred to as LED in the subsequent sections). This circle changes color (flash) in case of an on going communication. 3BDD011788R

32 Licensing Section 2 Application Licensing The DTM comes in two flavours, the Basic PROFIBUS DTM and PROFIBUS DTM Builder. PROFIBUS DTM Builder is the superset and includes the functionalities of Basic PROFIBUS DTM. The Basic PROFIBUS DTM allows handling the standardized functionality of PROFIBUS devices (mainly described through the GSD-file content and device manual content). This includes the functionalities as follows: Identification About Configuration (View of DPV1 services only) Observation (of DPV1 services) Online Parameterization (of DPV1 services) Call up user defined Applications, created with the DTM Builder( Administration (only read access) Registration The PROFIBUS DTM Builder allows furthermore to add GSD files, DPV1 parameters and profiles for DP, PA devices. It provides generic capabilities for defining device specific user interfaces (GUIs). The Basic PROFIBUS DTM/PROFIBUS DTM Builder offers convenient and userfriendly methods to identify, configure, parameterize and observe PROFIBUS DP and PA field devices. It is member of a family of universal DTMs. The key addition in the PROFIBUS DTM Builder is the Application Editor, which allows the user to specify his own graphic interfaces for the configured parameters. The generic control is invoked by the frame application. Proper controls for input boxes, text fields and buttons are generated as designed by the user. The user can then configure his own Interface; attach the controls to the available (and already configured) DPV1 parameters. The user configured GUI is displayed in online as well as in offline mode of the DTM. In online mode the user can fire a read or a write for the defined parameters. For more details refer to the section on the Application Editor. 32 3BDD011788R4101

33 Section 2 Application Licensing In this version the Basic PROFIBUS DTM / PROFIBUS DTM Builder only support DPV1 communication due to the fact that none of the available Master DTM supports cyclic DPV0 communication on its gateway channel. Due to this, DPV0 diagnosis will not be available in this version. Also HART Tool Routing (see specification HART on PROFIBUS) is not supported yet. 3BDD011788R

34 Graphical User Interfaces of the DTM Section 2 Application Graphical User Interfaces of the DTM The Basic PROFIBUS DTM/PROFIBUS DTM Builder provides graphical user interfaces to make the work with the DTM easy and convenient. The following GUIs are accessible from the user: Default View When using the ABB frame application Fieldbus Builder PROFIBUS/HART the Default View will be displayed as long as there is no DTM graphical user interface available and during a DTM application change. The default view is as shown in the Figure 2 below: Figure 2. The Default View for ABB Frame Applications 34 3BDD011788R4101

35 Section 2 Application About About This GUI gives the user basic information like the version of the DTM and the other required components etc. It also includes the copyright information and the licensing details. Figure 3. About DTM 3BDD011788R

36 Administration Section 2 Application Administration The Administration functionality provides a central place for the administrator tasks like inserting / deleting GSD files, managing data paths etc.this can be done only with the PROFIBUS DTM Builder license. Figure 4. Administration GUI Device Types The Basic PROFIBUS DTM is based on the content of the GSD file, which the user needs to insert before he can use the DTM. This part of the GUI is assigned specifically for this purpose. The DTM reads the basic information as supplied by the manufacturer and uses it to configure the device / give options for the configuration of the device to the user. The Basic PROFIBUS DTM license allows only to read the included GSD files. Inserting and deleting GSD files can be done with PROFIBUS DTM Builder license. 36 3BDD011788R4101

37 Section 2 Application Administration Insert GSD Delete GSD Scan GSD Maximal Number of GSD Actual Number. of GSD List of Device Types in use Invokes a dialog box for the user to select the GSD file he needs to insert. Once inserted the DTM stores the information of the GSD in its database and the user can then insert as many number of DTMs for that device type as he wants.multiple selection is possible. Allows the deletion of the information stored for a GSD. First the required device (GSD) is to be selected in the list of used GSD. Scans for the number of available GSDs in the hard disk and inserts them. This is only available when the DTM is acting as a Placeholder This button is now disabled but a user can select multiple GSDs in the insert. As per license a certain number of device types can be used with this DTM. This number is displayed here. This displays the actual number of the device types (GSDs) actually being used (inserted). Converted PA GSD files are not counted, but are created automatically from the DTM Builder during insertion. Displays the list of the devices whose GSDs are already inserted. 3BDD011788R

38 Administration Section 2 Application Figure 5. Administration GUI with the List of used GSDs To avoid corrupt data in the library of the frame application delete only GSD files from the list if you are sure that the device is not used in the complete system any more. Deletion of the own device GSD is not possible. The list of GSD will actually contain 2 entries per GSD file for a PA device inserted. One is the normal device name and the other appended with an YP0. The latter is specifically for the devices to be used with the LD 800P Linking Device. Direct inserting of an YP0 GSD file is prohibited. The user can select multiple GSD files in the dialog box to insert at the same time. Of course it is limited to the number of GSD allowed by the license. 38 3BDD011788R4101

39 Section 2 Application Administration The devices according to the inserted or deleted GSD files should be shown inside the library of the frame application after update of the frame applications library. If the new inserted devices are not shown inside the library of the system please refer to the Instruction Guide of the frame application for getting further information how to update the library. For example in some frame applications the library is updated only after closing and restarting the frame application. Device Data Export Import Actual Device type Allows the user to export the complete data for this instance of DTM (device) that has been configured into a file (extension.dtm). This includes the complete GSD information, configured modules, I/O parameters, user parameters, DPV1 parameters, user applications etc. This file can then be used via import to replicate this DTM Allows the import of the complete DTM data to replicate the DTM. Data can only been imported for the same device type as configured The actual device type used by this instance of the DTM DTM Data DTM Data Path Project Data Path GSD Information Displays the path used by this instance of the DTM to store data Displays the path used by the Basic PROFIBUS DTM/PROFIBUS DTM Builder for the required information on the devices inserted etc. The content of the selected device GSD is displayed 3BDD011788R

40 Identification Section 2 Application Identification The Identification function provides to the user basic information about the device. This information is derived from the GSD file that is inserted. It consists of three tabs: Information Definition Bus Information Figure 6. Information Tab of Identification 40 3BDD011788R4101

41 Section 2 Application Identification This tab is made of two frames: Device: The vendor related data is displayed Manufacturer Model Name Slave Family GSD File The Manufacturer Name The model of the device whose GSD used The profile on which the device is based Name of the GSD file inserted Revision levels: Hardware / Software PNO ident number GSD Revision This displays the Hardware and software revision PROFIBUS identification number The GSD revision The text box at the right is meant for adding some user comments. 3BDD011788R

42 Identification Section 2 Application Definition Figure 7. Definition Tab of Identification 42 3BDD011788R4101

43 Section 2 Application Identification The information displayed is: Slave Bus Address Freeze Mode Support Sync Mode Support This the address selected by the user when inserting the DTM. It is provided by the frame application via the parameter document. This will not be allowed to be changed by the user as it is managed by the frame application. Thus it will be simply displayed If the slave supports the freeze mode this will be enabled If the slave supports the sync mode this is enabled Modularity Modular Maximum no of modules Max no. of input bytes Max no. of output bytes Max no. of data bytes Module Offset If the slave is modular or a simple slave. If it is modular the box is checked The maximum number of the modules supported by the slave. This is the maximum number of bytes allocated by the slave for input values (parameters) This is maximum the number of bytes allocated by the slave for output values (parameters) This is the maximum number of bytes allocated by the slave for data values (parameters) Offset of the module. Here, the slot number is specified that is to appear in the configuration tool as the first slot number during configuration (used only for improved representation not within the DTM) 3BDD011788R

44 Identification Section 2 Application Watchdog Activated Time out (ms) Time base (ms) Shows whether the watchdog is activated or not The time in millisecond in which the watchdog expires The time base supported by the slave in milliseconds Unit Diagnostic Message Active Shows whether Message is activated for the unit diagnostic as per the GSD file Bus Figure 8. Bus Tab of Identification 44 3BDD011788R4101

45 Section 2 Application Identification This tab particularly displays the data related to the bus parameters. The values are again read from the GSD file. Special Parameters Redundancy Support FMS Support Fail safe Support Set Address Support Indicates whether or not the device supports redundant transfer technology Indicates whether or not an FMS/DP compound device relates to the device. DP device or FMS/DP compound device Indicates whether or not the slave accepts a data telegram without data instead of a data telegram with data. It is set to 0 in the PROFIBUS DP master class 1 CLEAR state. A data telegram without data is not accepted or a data telegram without data is accepted Indicates, whether or not the device permits bus address definition via the PROFIBUS (Function Set_Slave_Add). The bus address can only be updated directly on the device or the bus address can be updated on the device and via the PROFIBUS 3BDD011788R

46 Identification Section 2 Application Automatic Transmission Rate Detection A set of bus parameters can be calculated depending on the devices connected. There are two options for specifying the bus times. This is set by this option All bus times can be changed manually. In connection with the plausibility check, the set parameters are checked using the parameters of the connected slaves or the bus times are calculated using the parameters of the connected slaves. In this case the parameters in the dialog overlay cannot be changed. During the plausibility check, the bus times are recalculated using the parameters of the connected slaves Repeater Control Signal This value indicates the slot signal level CNTR-P 0 Not connected 1 RS485 2 TTL Protocol Ident Number This value indicates the device protocol identification. 1 PROFIBUS-DP Vendor specific 24 V pins This value indicates the meaning of the slot signals M24V and P24V 0 Not connected 1 Input 2 Output Min Slave Interval Max diagnostic data length This value indicates the least time interval between two slave list call-ups. The time basis for the value is 100 µs The maximum length (in bytes) for the diagnostic data Timing This frame lists the various transmission rates supported by the device along with the respective TSDR. With the stated transmission rate, a slave must respond at the latest within the time displayed (TSDR). 46 3BDD011788R4101

47 Section 2 Application Configuration Configuration The configuration function allows the user to configure the various DPV0 and DPV1 parameters for the device. This is available only in the offline mode as the user is not allowed to make any changes in online. It also allows configuring the modular slaves. The GUI is designed in a way that it allows separate the different parameters as per the modules and also it allows the user to define the IO data channels. The GUI contains 2 additional buttons as follows: This allows the user to check the parameters for errors. These include duplicate parameter names, overlapping memory areas etc. This check is done for all the parameters in all the tabs in the GUI. The same functionality is in [Apply] in which the data is saved too. By [Verify] the data is not saved. This allows the user to print the persistent parameters and their values to a connected printer. 3BDD011788R

48 Configuration Section 2 Application The configuration GUI consists of maximum 4 tabs (if DPV1 is activated, see Miscellaneous below). Figure 9. Miscellaneous Tab in Configuration Miscellaneous This tab allows the following configuration: Insertion of a specific user documentation link Automatic appendicy of a TAG to parameter names Activation of DPV1 parameter tabs Version designation for each specific XML file Adjustment of display view Documentation Link The user has the possibility to insert a link, which can refer to the specific device user documentation. The default link available is the ABB web site. However the user can enter any link and that is saved. The inserted link is opened if the frame application requests the documentation. 48 3BDD011788R4101

49 Section 2 Application Configuration Parameter TAG Enable the check box will map the given TAG name as a suffix to the specific parameter name in the Module tab. This can be done for all channels as well as for the DPV1 parameter if applicable. Suffix needs to have also a separator, recommended is a.. For example: TAG name is.m. Then the channel name for the specific channel from the module on position 2 is ChannelName.M2 The channel number is automatically appended to the suffix name. Do not use this feature, if the DTM is used in combination with the 800xA Asset Optimization software. Please see also the product documentation of PROFIBUS Device Integration, if this package is used. DPV1 Parameter To activate DPV1 parameter tabs, either for the complete device or for each single module, the DPV1 support must be enabled in the Miscellaneous tab. Use the check boxes in the DPV1 Parameter frame to enable the certain tabs. Enable at Device Coupler Enable at Device Module Activates the DPV1 parameter tab for the complete device. After activation a new tab card is visible as shown in Figure 9. Activates the DPV1 parameter tabs for the modules inside the Module tab. If already DPV1 parameters are included in the DPV1 grid, the tab can not be deactivated. Version of DPV1 and channel parameter Each saved configuration file of the DTM Builder contains two version information: A major version, which offers the possibility to create different XML files for the same device type (PNO ID). A minor version, which includes a version information in the existing XML file. Only the internal version information is changed to the adjusted number. 3BDD011788R

50 Configuration Section 2 Application Changing the major version results in a new XML file of the specific device type. Change the major version, if new functionality is available for a device type with the same PNO ID. Example for major version: The new device type is based on a new GSD revision with additional supported features. The new created XML file is represented in a new Sub-DTM of the Basic PROFIBUS DTM. Assignment of this DTM to a device type has to be done manually. If a new XML file version is created, a refresh of the DTM catalog in the FDT frame application is recommended. Both, the new and the old DTM version are included in the DTM catalog. The minor version saves the version information in the existing XML file. The minor version helps to have an internal versioning, if changes of the XML file have been performed. Minor version can not be modified by the user. A configuration change results in a new minor version inside the XML file. The DTM version box displays the version, used currently from the frame application. Value Display If the check box is marked, all parameters of data type Byte, Word or Dword are displayed in hexadecimal notation e.g. 16#0A in the following applications: Observe Parametrization User defined applications 50 3BDD011788R4101

51 Section 2 Application Configuration User Parameters Figure 10. User Parameters in Configuration The GUI displays a grid, which is populated with the parameters defined in the GSD file. The user cannot define own parameters. The specific information for the user parameters of the device is available from the device manual (documentation). The various values that need to be configured for each user parameter are also shown. The data types available are the basic PROFIBUS data types. These can be configured using the drop down list. The Value column is provided for the user to enter values for the user parameter. Since the DPV0 support is not available in the first version, the value entered by the user will be only utilized to configure the device.in brief the following attributes are required to be supplied for each parameter: 3BDD011788R

52 Configuration Section 2 Application If multiple parameter settings are needed, especially for configuration work during runtime, text strings and multiple parameters can be included in the Comment column. If the GSD file includes multiple configuration for user parameter, the value column and the comment column contains already the parameter settings. For example: The user needs a configuration for start and stop of a motor. This configuration can be done via user parameter. The user includes the parameter in the comment column like 0=On;1=Off. Now in the value column these both parameters are selectable via context menu. Figure 11. Multiple selection for user parameter 52 3BDD011788R4101

53 Section 2 Application Configuration Name Value Data Type Byte Bit Length Comment Name of the parameter (not modifiable in the first version) The value in decimal notation. For date type Octet String use value notation like 0A11. The 16# notation is not allowed to use here. The data type (PROFIBUS data types) to be selected from the drop down list (not modifiable) The byte position of the first byte within a structured byte field (not modifiable) The bit position of the first bit within a structured bit field (not modifiable) The total length (not modifiable) A free text that a user can enter for his reference and configuration of multiple parameter settings for the value column. DPV1 The same GUI also contains the tab for defining the DPV1 parameters. The user can add/edit/delete own parameters. He can also cut/copy/paste the parameters for quick entry. The copy paste feature allows inserting wrong parameters or overlapping memory areas. 3BDD011788R

54 Configuration Section 2 Application This grid is similar to the grid of the user parameters having the same basic functionality. However the attributes of the parameters are slightly different. The attributes are displayed in the following figures and described further on: Figure 12. DPV1 Parameters in Configuration 54 3BDD011788R4101

55 Section 2 Application Configuration Figure 13. DPV1 Parameters in Configuration: extended attributes Name Value Data Type Byte Bit Length Name of the parameter The value in decimal notation. The 16# notation is not allowed to use here. The data type (PROFIBUS data types) to be selected from the drop down list The byte position of the first byte within a structured byte field The bit position of the first bit within a structured bit field The total length in bit or byte depending on the data type of the parameter 3BDD011788R

56 Configuration Section 2 Application API Slot Index Access Load Load Sequence Persistent Min Value Max Value OPC Access OPC Short Name Comment This is another form of addressing used many times along with slot and index. Thus a space is provided for the user to enter the API value, which can be used for the parameters. This value will only be used during connect and disconnect to a device The position of the parameter in the device The index of the parameter in the specified slot The type of access read/write selectable via a drop down list The value Load is to identify whether the parameter is loaded with the operation download or not This is used to define the sequence in which the parameters are loaded via the download functionality. The value entered is taken as the sequence. In case of a structured parameter the sequence of the header is the same as the sequence of the parameters contained Persistent data is stored within the database of the frame application. All parameters with Load flag are persistent per default The minimum value the parameter can have The maximum value the parameter can have Whether the parameter is accessible via an OPC Server The short name of the OPC variable A free text that a user can enter for his reference 56 3BDD011788R4101

57 Section 2 Application Configuration The data type can be selected from the drop down list as shown below: Figure 14. DPV1 Parameters in Configuration: Data Types There are few additional buttons available on the grid. Check Import Export It checks for the correctness of the parameters added. This includes checking for duplicate names, memory overlapping areas etc. Allows the user to import an XML file containing the list of parameters (not available with Basic PROFIBUS DTM License). Allows the user to export the configured set of parameters to an xml file which can be used at a later date or for other devices (not available with Basic PROFIBUS License). 3BDD011788R

58 Configuration Section 2 Application The [Check] button checks only the DPV1 parameters while [Verify] button does it for the entire GUI for all the parameters (I/O, user parameters DPV1 etc.). Neither of them saves the data. Data is saved only by [Apply] and [Ok] buttons. The grid is locked when the license is not set to PROFIBUS DTM Builder license or the imported DPV1 parameter file is a read-only file or the user does not have sufficient rights. In this case only the data in the value column are changeable. For Bulk Data Management it is possible to insert the new values for the parameters in the grid and set the load flag and then download all these values into the device in one group. Module The module tab is specifically meant for the modular device. It allows the user to enter the modules at different positions and define the input/output parameters. Figure 15. Module Tab in Configuration 58 3BDD011788R4101

59 Section 2 Application Configuration On the extreme left the drop down list ( Selection ) displays a list of the modules available for the device (this information is as per the GSD file and cannot be modified). After selecting the module the user can select the position to which the module is assigned and can then use the [Insert] button to insert the module. On a successful insertion the details of the module are displayed in the right side of the GUI ( Information ). This is the description as provided by the manufacturer in the GSD file. At the bottom right the available number of bytes for input/output is displayed (again as defined by the manufacturer in the GSD file). Figure 16. Module Tab in Configuration: Channel Configuration 3BDD011788R

60 Configuration Section 2 Application If the number of bytes (input/output) is greater than zero, the user can select the input/output tabs respectively. The top of the tab displays the total number of bytes that can be configured for the same module. The grid available is similar to the DPV1 grid with the following fields: Name Type Byte Bit Length Number Protected Tag Comment Name of the parameter The data type (PROFIBUS data types) to be selected from the drop down list The byte position of the first byte within a structured byte field The bit position of the first bit within a structured bit field The total length A number from 1 to 64 to identify the channel for the diagnosis. 0 is the default value. Whether the channel is protected by channel assignment in the frame application or not. Do not set this flag manually! A meaningful tag attached to the channel. If nothing is inserted the name of the channel is taken. A free text that a user can enter for his reference For modules, supporting extended identifier format, the initial channel configuration is automatically done by the DTM. This configuration can be modified by the user. This modification will be saved and is included for further module configuration of the same device type. Without channel configuration the DTM does not provide the configured modules to the frame application. To provide a PROFIBUS master configuration via Basic PROFIBUS DTM, at least one module configuration must be done The input and output tab and the user parameter tab are similar in nature. They allow the user to enter the output and input parameters and user parameters specific to this module. The user parameters are read from the GSD file and only the value of the parameter can be changed. 60 3BDD011788R4101

61 Section 2 Application PROFIBUS Application Editor If the DPV1 parameter for module configuration is enabled in the Miscellaneous tab, additionally this DPV1 parameter tab is visible in the module tab. The configuration can be done for each module individual. The [check] button at the lower end can be used to check for the overlapping memory areas, duplicate parameters and length of data. To avoid corrupt data it is not possible to save the module configuration of the DTM until channel names are unique. A message is presented to the user to inform him about duplicate names he has to change before data are saved by [OK] or [Apply]. PROFIBUS Application Editor This editor is only available with the PROFIBUS DTM Builder license The Application Editor is an excellent tool for the user to customize the DTM according to his requirements. It allows the user to create his own GUI and allocate the required parameters to the GUI. He can have multiple tabs in a single GUI or multiple GUIs. 3BDD011788R

62 PROFIBUS Application Editor Section 2 Application First, the brief overview of the tool: Figure 17. Application Editor: Initial view The Builder GUI displayed has various sections. They are discussed in the order they need to be accessed. Manufacturer This lists the Manufacturer and device ID for which the application is to configure. One can select any required device shown in the list. So within this Builder GUI the user can create own GUIs for any other device not only the inserted one. The name of the device is built as: <PNO_Ident_Num><Device Name in GSD> 62 3BDD011788R4101

63 Section 2 Application PROFIBUS Application Editor Version Allows to create an application for a specific version of the device. A change in the application editor results in a new minor version, which is included in the XML file. Changing the major version results in a new XML file on the hard disc. For this device type, two different XML files and two different DTMs based on the PROFIBUS DTM Builder are available for the device type. Language Code The code of the language used in the new built GUI. Import This allows the user to import a xml file containing the application details. This application is amended to the existing application. Load This allows the user to load a completely new application file. The existing application is closed. The application, which was open before loading, is overridden from the new application during close or save. Application Explore This section lists the various applications already configured/available. In the GUI it is shown as application AT1. In case of no application existing, one can be added by right click on the top entry. In order to edit an existing application select the required application. 3BDD011788R

64 PROFIBUS Application Editor Section 2 Application Once selected the GUI looks like the following figure. The application layout window contains the selected GUI or a blank form in case of a new application. Figure 18. Application Editor: Sample GUI The explorer shows the hierarchical structure of the graphical elements and functions. When creating a new GUI, first add a new object to the application explorer bearing the name of the application: 1. Click with the mouse to select the uppermost node in the object tree. 2. Click the right mouse button to activate the "Add Application" button. 3. Press the button to add a new application object. 64 3BDD011788R4101

65 Section 2 Application PROFIBUS Application Editor Example: Another application is to be added to the existing applications (AT1). The application object now requires the following entries to be made (see properties) to complete the description. 4. Change the default name, i.e. enter the actual name of the application. 5. Select the appropriate user role for the application. 6. If available, enter the path to a help file. 7. Select the operating mode. 8. Select a module. 3BDD011788R

66 PROFIBUS Application Editor Section 2 Application It is easier to carry out actions affecting a number of graphical elements (copying, moving, deleting, etc.) in the explorer than in the application layout. Changes to the object layout in the tree are automatically applied to the layout and vice versa. Toolbox It contains the various controls that can be dragged and dropped on the form in application layout. These can be different tabs, text boxes, labels, buttons etc. As of now the button in the toolbox does not have any functionality added. Button Has no functionality for PROFIBUS. Parameter DPV1 parameter for input or output of device data. Label, comment and CSV path are optional. Properties: Name Variable Label Comment CSV Freely selectable name under which the explorer manages the graphical element Reference to the DPV1 parameter (variable) according to the DPV1 editor parameter list Descriptive name of the parameter on the user interface Comment (e.g. engineering unit as constant) Path to a.csv file that contains language independent strings for single values. 66 3BDD011788R4101

67 Section 2 Application PROFIBUS Application Editor Example: Label, variable, CSV and comment all together create a graphical element, which can be positioned very easily on the application layout. Example: The "Comment" in the "Properties" has been deleted for the first element that is to display the parameter value. The second element is used simply to read the associated physical unit. The label and comment are therefore superfluous. 3BDD011788R

68 PROFIBUS Application Editor Section 2 Application The application reads the current unit and value from the field device in online mode. The inserted CSV path allows the user to give certain strings to value. Instead of the values the strings will be shown in the user defined GUI as shown below. As described above the parameter may have enumerated values as defined by the user. In that case, the user needs to put the values in a.csv file (a large number of enumerations are already supplied along with the setup). The path of the CSV file is specified in the properties of the text box as displayed in the figure below. Once specified the values are taken from the CSV file and displayed accordingly. This is a useful functionality if a text e.g. Mode Automatic should be presented to the user as a string Automatic instead of the according value 1. The user can specify via the key words appl.path (to use the application path) or project.path (to use with the project related path) if the file is residing in or relative to the application path or the unique project related path. This way it is easy to port the application across different machines. But in porting the CSV file needs to be transferred as well and stored in the appropriate path. 68 3BDD011788R4101

69 Section 2 Application PROFIBUS Application Editor Example of a.csv file for an Actuator Action: Value, 0x0409 (English), 0x0407 (German) Required header. To extend for next language insert language code 0x0xxx (name) 0, not initialized, nicht initialisiert 1, opening 100%, öffnen 100% 2, closing 0%, schliessen 0% 3, none/ remains in actual position, kein/ bleibt in der aktuellen Position Frame Frame for grouping elements that belong together in terms of their function. Used primarily to group parameters and buttons. Properties: Name Border Name under which the Explorer manages the graphical element and also the descriptive name on the user interface True = with border; False = without border Example: 3BDD011788R

70 PROFIBUS Application Editor Section 2 Application Label Descriptive text, which can be assigned to the other graphical elements if required. Properties: Name Name under which the Explorer manages the graphical element and also the descriptive name on the user interface Example: Picture Image (file) in J(E)PG format, which can either be used as background or at the same level with parameters or other elements. Properties: Name Path Name under which the Explorer manages the graphical element The Editor saves the path and the image in the _app.xml file. When an import/export is carried out, this means that the image is transferred to the other computer or storage medium and appears there. 70 3BDD011788R4101

71 Section 2 Application PROFIBUS Application Editor Example: Tab card Tabs for dividing an application into a number of subfunctions. Properties: Name Number Name under which the Explorer manages the tab card and also the descriptive name on the user interface The number indicates the position of the tab card. Up to three tabs can be used in one application. Example: 3BDD011788R

72 PROFIBUS Application Editor Section 2 Application Alarm An alarm button is available for the toolbox. This can be used to indicate via different colors about the out of limit values of the parameter after assigning the ranges, min and max values. The alarm can display different colors. We can define different values for the different colors as shown below. Properties: Name Variable Name Red_min, Red_max Name under which the Explorer manages the tab card and also the descriptive name on the user interface Reference to the DPV1 parameter (variable) according to the DPV1 Editor parameter list Color that is displayed when a value is greater or less the configured value. Example: 72 3BDD011788R4101

73 Section 2 Application PROFIBUS Application Editor Application Properties For the new application the designer can specify the name as well as the user rights, a help file, module and the operation phase in which the new generated GUI should be shown. Properties Name User Level Operating Mode Help File Module Name of the application Selectable user rights for access are: Operator, Observer, Maintenance, Planning Engineer. Operation phase in which the application is shown. Possible operation phases are: online, offline or off-/online. Path to help file that should be shown with this application. Selectable modules of the device. If a specific module is configured the belonging application is shown. If no module is selected the application is shown always. The Help file has to be a.chm Microsoft compatible help file. The user can specify via the key words appl.path (to use the application path) or project.path (to use with the project related path) if the file is residing in or relative to the application path or the unique project related path. This way it is easy to port the application across different machines. But in porting the Microsoft help files (*.CHM) file needs to be transferred as well and stored in the appropriate path. 3BDD011788R

74 PROFIBUS Application Editor Section 2 Application Application Layout Once a control is put on the form, all its properties can be viewed in the properties frame. This also contains e.g. a list of DPV1 parameters (configured in the configuration GUI) that can be assigned to a text box etc. Figure 19. Application Editor: DPV1 Parameter List in Properties For example if a text box is inserted the user can assign it to a DPV1 parameter so that during offline/online he can modify/view the values corresponding to the parameter. 74 3BDD011788R4101

75 Section 2 Application Invoke User Defined Applications Invoke User Defined Applications Once saved, the application is available in the list of offline/online functions. Figure 20. Application Editor: Application available in function list When selected the previously configured GUI will look like the following figure in the following chapter. User defined GUI As mentioned above the user can create own GUIs with the Application Editor according to own needs. These GUIs are available for the user according to the user rights and the online or offline phase of the DTM. The user defined GUIs are available as templates. Either the customer can create own template pool of user defined GUIs or he can retrieve from ABB a predefined template pool. 3BDD011788R

76 User defined GUI Section 2 Application If the DTM starts and it detects such a user defined GUI for its device in the template pool, it will provide this GUI accessible as a function of its DTM. Example for a user defined application in offline mode: Figure 21. User Defined GUI Offline: User GUI In offline mode the user defined GUI will start with the last stored values for the persistent data. Here the user can now change these default values and write them to the device either by a download or a write action in the user defined GUI. 76 3BDD011788R4101

77 Section 2 Application User defined GUI Example for a user defined application in offline mode: Figure 22. User Defined GUI Online: User GUI Inside GUI the user can fire a read/write for the parameters on the GUI (in online mode). If DPV1 parameters are read-only parameters the value filed is disabled and greyed. Read Cyclic This allows the user to read the values for the parameters on the GUI cyclically. The interval of the cyclic read can be set in the Windows registry. Typically it is 5 seconds. This interval is automatically recalculated and extended if all the values cannot be read in 5 seconds. 3BDD011788R

78 Online Functions Section 2 Application Online Functions Observe The observe GUI is a standard GUI that comes along already with the Basic PROFIBUS DTM license apart from the user defined GUIs. Observe allows the user an easy way to read the values of the DPV1 parameters from the device. The user can configure the parameters that need to be observed. The GUI is as follows: Figure 23. Observation As displayed, the defined DPV1 parameter list (readable parameters) is displayed on the left grid (labelled as parameter list) and the user can select the parameters he wants to observe and put them in the right grid called Read Value (via the right arrow [>] button). No value of the data is displayed at the start up. When the user invokes Read or selects Read Cyclically the parameters values are requested from the device via the frame application. 78 3BDD011788R4101

79 Section 2 Application Online Functions The General Status box at the bottom displays the current status of the read procedure. The box will also display any error code that is returned by the bus in case of a read error. Once the connection to the device is established the green LED at the middle of the status bar starts flashing. If the read cyclically check box is enabled, the selected DPV1 parameters (parameters in the right grid) for observations are read cyclically until the check box is disabled or the GUI is closed. The cycle for the successive reads is defined in the registry and is typically 5 sec. However in case the number of parameters selected is more and one read cycle is not completed in 5 seconds, the subsequent cycle is skipped without causing any errors. For selecting multiple parameters to be shifted to the Read Value grid, one can press shift and select multiple parameters. However the structure headers cannot be shifted due to the fact that headers are a logical grouping and the constituent parameters are the actual parameters. This is visible in the following figure. Figure 24. Observe: Data Read 3BDD011788R

80 Online Functions Section 2 Application This figure also displays how the values will look like after being read. In case the configured data length does not match the length returned by the device the grid displays the text Data Length Mismatch in red. User is requested to check up the configuration of the parameter. More detailed information is given within the General Status box. There the specific PROFIBUS error code can be read. Although the parameter list grid does not display the complete details of the parameter (only name and data type are displayed), once selected (transferred in the Read Value grid) the other attributes like slot and index values are also visible by scrolling to the right (see bottom figure). Any parameter or multiple parameters can be deselected via the left [<] button which transfers them to the Parameter List grid. The logic takes care of arranging the parameters to their respective structure positions. User can also save the selected list via the [Apply] button so that next time the GUI is displayed the parameter list remains intact. Figure 25. Observe: Parameter attributes displayed 80 3BDD011788R4101

81 Section 2 Application Online Parameterization Online Parameterization The GUI does not allow any editing. Any changes that need to be made in the configuration have to be done in the offline phase (Configuration GUI). Pressing the [Cancel] button will disconnect the DTM from the device and stop cyclic read. Online parameterization allows the user to enter the values of the DPV1 parameters and write them to the device. The online parameterization GUI is a standard GUI that comes along already with the Basic PROFIBUS DTM license apart from the user defined GUIs. Figure 26. Onine Parameterization 3BDD011788R

82 Online Parameterization Section 2 Application As displayed the defined DPV1 parameter list (writable parameters) is displayed on the left grid (labelled as Parameter list) and user can select the parameters he wants to parameterize and put them in the right grid called Write Value (via the right arrow [>] button). The last value that was read from the device is displayed. User is allowed to edit the value. When the user invokes Write the parameters values are sent to the device via the frame application. The General Status box at the bottom displays the current status of the write procedure. The box will also display any error code that is returned by the bus in case of a write error. Once the connection to the device is established the green LED at the middle of the status bar starts flashing. For selecting multiple parameters to be shifted to the Write Value grid one can press shift and select multiple parameters. However the structure headers cannot be shifted due to the fact that headers are a logical grouping and the constituent parameters are the actual parameters. When the user enters a value and fires a write the value is checked for the validity (data type, range are checked). The color of the text remains blue. If the write was successful the color changes to black else it changes to red. More detailed information is given within the general status box. There the specific PROFIBUS error code can be read. Although the Parameter list grid does not display the complete details of the parameter (only name and data type are displayed), once selected (transferred in the Write Value grid) the other attributes like Slot and index values are also visible by scrolling to the right (see bottom figure). Any parameter or multiple parameters can be deselected via the left [<] button which transfers them to the Parameter List grid. The logic takes care of arranging the parameters to their respective structure positions. User can also save the selected list via the [Apply] button so that next time the GUI is displayed the parameter list remains intact. When a write only parameter is selected for writing, all the parameters belonging to the same slot and index are selected (shifted to the right grid). Additionally the value that needs to be put should be decimal. If the value to be written is hex it has to be prefixed with 0x or H. The GUI does not allow any editing. Any changes that need to be made in the configuration have to be done in the offline phase (Configuration GUI). 82 3BDD011788R4101

83 Section 2 Application Online Compare Pressing the [Cancel] button will abort the communication. Online Compare Online compare is a great feature to know the difference between the values residing in the Instance Database of the frame application and the device. Instance database is the storage place that is used by the DTM to store the persistent parameters. The user can invoke online compare to compare the values in the local database and the device. First the looks of the GUI are shown and described. Figure 27. Online Compare As the figure shows, the user gets a list of the DPV1 parameters configured (only readable and persistent). Their data type, slot and index are shown too. The next two columns are for the local data and device data. Of course, the device data is empty as of now as the user needs to fire a read to get all the values from the device (via the [Read Data] button). The general status box displays the status of the read. Once the connection is established the LED in the centre of the status bar flashes. Once 3BDD011788R

84 Online Compare Section 2 Application the values are read they are displayed in the device data column. If the values of the two columns (instance data and device data) differ, the extreme left column State highlights it via an icon. This is shown in the following figure. Figure 28. Online Compare: Result The values must have been downloaded at least once for the online compare to be successful. Also the parameter configuration should be identical to the one existing in the device, if not then online compare will not succeed. The comparison of float values takes into account a band of 1% for them to be assumed equal. Also no changes are allowed in the GUI. The GUI does not allow any editing. 84 3BDD011788R4101

85 Section 2 Application Non-GUI Applications Non-GUI Applications There are certain functions that are supported by the DTM but are available from the frame application. They do not have a dedicated graphical user interface but are available via a context menu from the frame application. Following are the ones that do not have a dedicated graphical user interface but are still available. Upload Download During an upload, all DPV1 parameters are read from the field device and saved to the corresponding instance data record. An upload can be used for commissioning (initial startup) if a device-specific configuration is not available (planning phase), meaning that the instance data record only contains the default values. An upload during commissioning reads the factory-set data from the field device and writes it to the instance data record. The application has no GUI and it is called directly by the frame application e.g. for bulk data management. An upload completely overwrites the data in the instance data record. If concrete parameter values have already been loaded to the database (instance data record) during the planning phase by means of the configuration, these can be written to the field device by performing a download. The online parameterization application can be used to write data selectively. This application is useful if factory-set data such as the process point, serial numbers, etc. is not to be overwritten with the default values from the instance data record. The application has no GUI and it is called directly by the frame application e.g. for bulk data management. A download completely overwrites the data in the field device. Online Compare Online compare is also available as a non-gui function from the frame application. It compares the complete set of device DPV1 parameters. The instance data stored in the database are compared with the same set of data uploaded from the field device. 3BDD011788R

86 OPC Access Section 2 Application The application returns FALSE to the frame application in case of conflicting values. The application has no GUI and it is called directly by the frame application e.g. for bulk data management. The values must have been downloaded at least once for the online compare to be successful. Also the parameter configuration should be identical to the one existing in the device, if not then online compare will not succeed. OPC Access If during configuration phase the OPC access flag within the DPV1 parameter grid was set, then these parameters can be accessed from the ABB OPC Server PROFIBUS/HART. The OPC Server will request a list of accessible DPV1 parameters from the DTM, then it will start the reading and/or writing of these parameters. Print actual data If supported by the frame application, the DTM allows the user to print out the actual set of persistent stored data and their actual values. Audit Trail For purposes of data logging within the frame applications audit trail function, the DTM provides in mode offline as well as in mode online the changed data with time stamp and user information. Additionally the start and end of complete functions such as download and upload of the device are logged. The frame application has to provide the optional FDT audit trail to use this function of the DTM. Export/Import of data For purposes of data export and import of the DTM from one project to another project of the same frame application, the DTM provides the functions export and import for the frame application. The important data of the DTM are exported to a data stream, which is under control of the frame application and imported from this stream. 86 3BDD011788R4101

87 Section 2 Application Placeholder Placeholder The placeholder DTM is a Basic PROFIBUS DTM/PROFIBUS DTM Builder with limited functionality. It is used in a project only once a time when no GSD file is imported and known to the DTM. Figure 29. Placeholder If none GSD file is inserted to the Basic PROFIBUS DTM/PROFIBUS DTM Builder yet it will only show the placeholder in the library of the frame application. How to work with the Placeholder 1. First the user has to insert the placeholder in the topology tree of the frame application and to start the administration functionality. 2. Inside the administration functionality the user has to select and insert via [Insert GSD] the GSD files for the devices he wants to work with. 3. After inserting the GSD files the user can e.g. change the license within the Registration GUI. 4. Next important step is to remove the placeholder from the topology tree of the frame application again and to start an update of the frame applications library. The placeholder DTM has to be removed from the topology tree of the frame application before the project is verified or going online otherwise an error message will be sent to the user. 3BDD011788R

88 Templates and Profiles Section 2 Application Now the new devices according to the inserted GSD files should be shown inside the library of the frame application. If the new inserted devices are not shown inside the library of the system please refer to the Instruction Guide of the frame application for getting further information how to update the library. For example in some frame applications the library is updated only after closing and restarting the frame application. Templates and Profiles The DTM provides two possibilities to configure DPV1 parameter, user application etc. for a specific device. The user can import dependent on his license profiles for DPV1 parameter configuration or additionally special DPV1 parameter and user applications. Profiles Templates If the user has only the Basic PROFIBUS DTM license he can import via [Import] in the DPV1 grid predefined DPV1 parameter profiles e.g. PROFIBUS-PA-Profiles. These profiles are provided by ABB and cannot be changed. Only the parameter values can be changed. The user can find the predefined profiles in the directory: <Installation Directory>\Profile After saving the configuration these DPV1 parameters were made device specific and when the DTM is called next time these data are shown directly. If the user has PROFIBUS DTM Builder license he can import via [Import] in the DPV1 grid predefined DPV1 parameter profiles e.g. PROFIBUS-PA-Profiles and predefined templates as well as self defined DPV1 parameter files. In the Application Editor the user can import or load via [Import] or [Load] the user application files and self defined user application files. These predefined profiles, templates and user applications are provided by ABB and can be changed. 88 3BDD011788R4101

89 Section 2 Application Templates The user can find the predefined profiles in the directory: <Installation Directory>\Profile The predefined templates and user applications are in the directory: <Installation Directory>\Templates During start of the DTM for the first time all predefined templates and user applications are copied to the main path of the project (project related path) automatically. After saving these files inside a specific device DTM these templates and user applications were made device specific and when the DTM is called next time these DPV1 parameters and user applications are shown directly. License Profiles Templates Basic PROFIBUS DTM PROFIBUS DTM Builder Predefined Only values changeable Predefined Self defined Parameter and values changeable Predefined user applications Only values changeable Predefined - User applications - DPV1 parameters Self defined - User Applications - DPV1 parameters Parameter, values and applications changeable 3BDD011788R

90 Templates Section 2 Application 90 3BDD011788R4101

91 Appendix A Data Types Simple 1. Unsigned8 (Byte) See DPV1-Ext., (Code 5). Value Range: Unsigned16 See DPV1-Ext., (Code 6). Value Range: Unsigned32 See DPV1-Ext., (Code 7). Value Range: Real See DPV1-Ext., (Code 8). Value Range: refer to IEEE Std 754 Short Real Number (32 bits). In case the number read from device is an Infinity or Not a Number it is displayed H7FFFFFFF For +QNAN or +Infinity HFF7FFFFFFor -QNAN or Infinity Additionally a message is displayed in the general status box as +QNAN error with the parameter name 5. VisibleString See DPV1-Ext., (Code 9). VisibleString is a field of characters. All characters must be less then 0x OctetString See DPV1-Ext., (Code 10). OctetString is a field of characters. All characters have no limit in range. 3BDD011788R

92 Appendix A Data Types 7. Word Value Range: 0 HFFFF 8. Dword Value Range: 0 - HFFFFFFFF 92 3BDD011788R4101

93 INDEX 24 V Pins 46 Numerics About 35 Acyclic Data Exchange 26 Administration 36 Alarm 72 API 56 Application Explore 63 Application Layout 74 Application Properties 73 Audit Trail 86 Automatic Transmission Rate Detection 46 A B Basic PROFIBUS DTM 11 Bus 44 Bus Address 43 Buttons 29 C Channel Configuration 59 Configuration 25 Copyright Information 35 Cyclic Data Exchange 26 Data Storage 26 DDL 11 Default View 34 Definition 42 Delete GSD 37 D Device Data 39 Device Description Language 11 Device Master Data 24 Device Type Manager 11 Device Types 36 Download 85 DPV1 53 DTM 11, 15 DTM Data 39 Export 57 Export/Import 86 E F Fail Safe 45 FDT 11, 15 Field Device Tool 11 Fieldbus Builder 11 Frame Application 11, 27 Freeze Mode 43 G Graphical User Interface 11, 34 GUI 11 Help File 73 Import 57 Index 56 Industrial IT 11 H I 3BDD011788R

94 Index Information View 40 Input/Output Boxes 30 Insert GSD 37 L Label 70 Language Code 63 LD 800P Linking Device 38 License Key 17 Licensing 32 Load Sequence 56 M Max Diagnostic Data Length 46 Min Slave Interval 46 Modularity 43 Module 58 O Observation 78 Online Compare 85 Online Parameterization 81 OPC Access 56, 86 P Parameterization 26 Persistent 56 Picture 70 Placeholder 87 Print 86 PROFIBUS 21 PROFIBUS DTM Builder 12 PROFIBUS-DP 21 PROFIBUS-DP States 25 PROFIBUS-FMS 21 PROFIBUS-PA 21 Profiles 88 Protocol Ident Number 46 R Registration 17 Repeater Control Signal 46 Revision Level 41 Scan GSD 37 Set Address 45 Slave Data 23 Slot 56 Special Parameter 45 Status Bar 31 Sync Mode 43 System Application 12 Tab card 71 Templates 88 Timing 46 Toolbox 66 Unit Diagnostic 44 Upload 85 User Interfaces 27 User Parameter 51 User Roles 28 S T U V Vendor Related Data 41 Watchdog 44 W 94 3BDD011788R4101

95

96 3BDD011788R4101. Printed in Germany May 2005 Copyright by ABB. All Rights Reserved Registered Trademark of ABB. Trademark of ABB. Automation Technology Products Västerås, Sweden Automation Technology Products Wickliffe, Ohio, USA Automation Technology Products Mannheim, Germany