gfk6372d cimplicity configuration tools

GEMIS Tools for CIMPLICITY

Configuration Tools forUsing CIMPLICITY HMI in GEMIS Equipment

GEH-6372D(Supersedes GEH-6372C)

1998 by General ElectricCompany, U.S.A. All rightsreserved. Printed in the UnitedStates of America.

These instructions do not purport to cover all details or variations in equipment, norto provide for every possible contingency to be met during installation, operation,and maintenance. If further information is desired or if particular problems arise thatare not covered sufficiently for the purchasers purpose, the matter should be referredto GE Motors & Industrial Systems, Salem, VA.

This document contains proprietary information of General ElectricCompany, USA and is furnished to its customer solely to assist thatcustomer in the installation, testing, operation and/or maintenance ofthe equipment described. This document shall not be reproduced inwhole or in part nor shall its contents be disclosed to any third partywithout the written approval of GE Motors & Industrial Systems.

Issue Date: January 1998Revision C: December 1997

GEMIS Tools for CIMPLICITYConfiguration Tools forUsing CIMPLICITY HMI in GEMIS Equipment

SAFETY SYMBOL LEGEND

Indicates a procedure, practice, condition, or statement that, if not strictlyobserved, could result in personal injury or death.

Indicates a procedure, practice, condition, or statement that, if not strictlyobserved, could result in damage to or destruction of equipment.

NOTE

Indicates an essential or important procedure, practice, condition, or statement.

ARCNET is a registered trademark of Datapoint Corporation.Ethernet is a trademark of Xerox Corporation.CIMPLICITY is a trademark of GE Fanuc Automation North America, Inc.IBM is a registered trademark of International Business Machines Corporation.PC is a registered trademark of International Business Machines Corporation.Series 90 is a trademark of GE Fanuc Automation North America, Inc.Windows is a registered trademark of Microsoft Corporation.Windows NT is a registered trademark of Microsoft Corporation.

WARNING

CAUTION

GEH-6372D GEMIS Tools for CIMPLICITY Contents i

ContentsChapter 1 Overview 1

Introduction................................................................................................................................1Before Beginning .......................................................................................................................1

Organization.................................................................................................................1Conventions .................................................................................................................3

Chapter 2 Installation 5Introduction................................................................................................................................5PC Requirements........................................................................................................................5Software Products ......................................................................................................................6Installing the Tools.....................................................................................................................7

License Agreement.......................................................................................................8Products Installed.......................................................................................................10SDB Information........................................................................................................12

Uninstall Programs...................................................................................................................12Upgrading From an Earlier Version .........................................................................................13

Chapter 3 System Database (SDB) Utilities 15Introduction..............................................................................................................................15Concepts...................................................................................................................................16Using SDB Utilities..................................................................................................................17

SDB Utility Menus.....................................................................................................17Configuration ...........................................................................................................................21

CIMPLICITY HMI Project .......................................................................................21CIMPLICITY Server (topology) ...............................................................................22SDB Server ................................................................................................................26Resource List .............................................................................................................27

Exporting Routing Tables ........................................................................................................28Importing Signals and Alarms..................................................................................................29

SDB Signals (Points) .................................................................................................29Import Signals (Points) ..............................................................................................32.csv File...................................................................................................................... 33Import Alarms............................................................................................................34

ii Contents GEH-6372D GEMIS Tools for CIMPLICITY

Chapter 4 Mode Logger 39Introduction ............................................................................................................................. 39Concepts .................................................................................................................................. 39

Mode Logger (Modelogr.exe) .................................................................................. 40Message Archiver (MsgArchiver.exe) ...................................................................... 41Fault Text Database .................................................................................................. 41Message Archiver Database ...................................................................................... 41

Configuration........................................................................................................................... 42Mode Logger Settings ............................................................................................... 43Message Archiver Settings........................................................................................ 44

PCLG Assembly...................................................................................................................... 45Settings...................................................................................................................... 46Memory Conflicts and BIOS Problems..................................................................... 47

Troubleshooting ...................................................................................................................... 48

Chapter 5 DlanView 49Introduction ............................................................................................................................. 49Concepts .................................................................................................................................. 49

Data Flow.................................................................................................................. 50Message Colors ......................................................................................................... 50

Using DlanView...................................................................................................................... 51View Menu................................................................................................................ 52Setting Menu............................................................................................................. 53

Configuration........................................................................................................................... 54Database Locations ................................................................................................... 54Display Settings ........................................................................................................ 55Operation .................................................................................................................. 56

Examples ................................................................................................................................. 60Single Column Search............................................................................................... 61Multiple Column Search ........................................................................................... 62Wildcard Searches .................................................................................................... 65

Chapter 6 Network Time Protocol (NTP) 67Introduction ............................................................................................................................. 67Concepts .................................................................................................................................. 67

GE Master Time Server ............................................................................................ 67Operation Modes....................................................................................................... 68

Using NTP............................................................................................................................... 68Configuration........................................................................................................................... 70

Broadcast Time Master Node Setup ......................................................................... 70Unicast Master Node Setup....................................................................................... 71Broadcast Client Node Setup .................................................................................... 73Unicast Client Node Setup ........................................................................................ 74Programs ................................................................................................................... 75ntp.ini File ................................................................................................................. 75Startup Option ........................................................................................................... 77Service Program........................................................................................................ 77

GEH-6372D GEMIS Tools for CIMPLICITY Contents iii

Operation..................................................................................................................................79Monitoring .................................................................................................................81

NTP Diagnostics ......................................................................................................................82Startup........................................................................................................................82Configuration .............................................................................................................83Operation ...................................................................................................................84

NTP Status Indicator ................................................................................................................85Operation ...................................................................................................................85

Chapter 7 Alarm Manager Service 87Introduction..............................................................................................................................87Concepts...................................................................................................................................87Using GECAMS.......................................................................................................................89

Chapter 8 Diagnose 91Introduction..............................................................................................................................91Concepts...................................................................................................................................91Using Diagnose ........................................................................................................................93

Menus Commands......................................................................................................95Toolbar Commands....................................................................................................98Settings.......................................................................................................................98

Configuration .........................................................................................................................104Startup......................................................................................................................104Command Line Arguments ......................................................................................104Live Diagnostic........................................................................................................105

Diagnostics Examples ............................................................................................................106Fault Diagnostics .....................................................................................................108Live Diagnostics ......................................................................................................112File Diagnostics .......................................................................................................112

Chapter 9 DLAN+ Devcom 113Introduction............................................................................................................................113

Requirements ...........................................................................................................114Concepts.................................................................................................................................115PCA198 Hardware Settings....................................................................................................115

Node Address (SW1) ...............................................................................................116Interrupt Request Setting (E1) .................................................................................116I/O Port Address (E3) ..............................................................................................112Memory Address (E4)..............................................................................................117

Using DLAN+ Devcom..........................................................................................................118PCA198 Boards .......................................................................................................119

Configuration .........................................................................................................................122Setup the CIMPLICITY HMI Server.......................................................................123Setup the UC2000 ....................................................................................................125Setup the CIMPLICITY HMI Project ......................................................................126Setup the SDB Utilities ............................................................................................138

Uninstall .................................................................................................................................139Troubleshooting .....................................................................................................................140

iv Contents GEH-6372D GEMIS Tools for CIMPLICITY

Chapter 10 DLAN+ Status Monitor 141Introduction ........................................................................................................................... 145Concepts ................................................................................................................................ 145Using DLAN+ Status Monitor .............................................................................................. 147

Menus Commands................................................................................................... 147Configuration......................................................................................................................... 149

Database Location................................................................................................... 149DLAN+ ............................................................................................................... 149Display Size ............................................................................................................ 150Status Bar ................................................................................................................ 150

Troubleshooting .................................................................................................................... 150

Appendix A CIMPLICITY HMI 151

Appendix B SDB Utility Detail Information 155DLAN+ Configuration Registry Data.................................................................................... 155Example Routing Table......................................................................................................... 157Mapping Between an SDB Signal and a CIMPLICITY HMI Point ...................................... 158Details and Example .csv Files.............................................................................................. 160Mapping Between SDB Alarms and CIMPLICITY Alarm................................................... 162System Level Activities Required to Import Signals into the CIMPLICITY HMI PointDatabase ................................................................................................................................ 164System Level Activities Required to Import Alarms into the CIMPLICITY HMI PointDatabase ................................................................................................................................ 165

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 1 Overview 1

Chapter 1 Overview

IntroductionWindows 95 is currently notsupported.

This manual describes the General Electric Motors & Industrial Systems (GEMIS)Tools for CIMPLICITY. This is a set of Windows NT software applications,which run on an IBM PC compatible personal computer (PC). The toolscompliment the CIMPLICITY Human-Machine Interface (HMI) in projectdevelopment and control of GEMIS.

To prevent personal injury or equipment damage caused byequipment malfunction, only adequately trained personnel shouldmodify any programmable machine.

Before BeginningWindows-based screenborders may vary inappearance.

This manual describes the features of the GEMIS Tools for CIMPLICITY andpresents step-by-step procedures for using the software applications provided. Itpresumes that the user has already installed Windows NT. This manual also assumesthat the user possesses at least a medium-level knowledge of Windows. Hardwarerequirements and instructions for installing the GEMIS Tools for CIMPLICITY arein Chapter 2.

OrganizationThis manual is organized as follows:

Chapter 1 Overview. Provides a functional overview of the different applicationscontained in the GEMIS Tools for CIMPLICITY.

Chapter 2 Installation. Describes the hardware required to operate theapplications. It also provides procedures for installing the software into the PC andconnecting the PC to the control system.

Chapter 3 SDB Utilities. Provides tools to import/export and verify data to andfrom the CIMPLICITY HMI project point database.

WARNING

2 Chapter 1 Overview GEH-6372D GEMIS Tools for CIMPLICITY

Chapter 4 Mode Logger. Provides procedures for using the Mode Loggerapplication to capture messages on the drive local area network (DLAN+).Chapter 5 DlanView. Provides procedures for using the DlanView application toview the status of drops on a partcular DLAN+.

Chapter 6 Network Time Protocol (NTP). Provides procedures for using theTime Synchronization application to coordinate time between PCs in a CIMPLICITYHMI project.Chapter 7 Alarm Manager Service. Provides set up procedures for the AlarmManager Service, which receives messages from the Message Archiver and sendsthem to the CIMPLICITY HMI Alarm Manager.

Chapter 8 Diagnostics. Provides procedures for using the Diagnose application,which translates fault diagnostic messages from DlanView.

Chapter 9 DLAN+ Devcom Provides procedures for enabling the CIMPLICITYHMI system to directly access data from the DLAN+.

Chapter 10 DLAN+ Status Monitor. Provides procedures for using the StatusMonitor to view the status of the drops on a particular DLAN+.

Appendix A CIMPLICITY HMI. Describes the CIMPLICITY HMI Server andViewer with Mode Logger.

Appendix B SDB SDB Utility Detail Information. Provides detailed informationfor the SDB Utility, including examples and system level activities.

Glossary. Provides definitions of configuration terms and tool concepts.Refer to the Table of Contents for the organization of these chapters.

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 1 Overview 3

ConventionsThe following conventional terms, text formats, and symbols are used throughout thisdocumentation for the described applications.

Convention MeaningBold Indicates that the word is being defined.

Arial Bold Indicates the actual command or option that is chosen from amenu or dialog box. The command can also be a key to press.

Italic Indicates a word used as a word or a letter used as a letter. Forexample, the display should now read SDB has stopped. Italicalso emphasizes new terms, margin notes, and the titles offigures, chapters, and other books in the toolbox package.

UPPERCASE Indicates a directory, filename, or block name. Lowercase letterscan be used when typing names in a dialog box or at thecommand prompt, unless otherwise indicated for a specificapplication or utility.

Monospace Represents examples of screen text or words and characters thatare typed in a text box or at the command prompt.

Indicates a procedure.w Indicates a procedure with only one step.

Indicates a list of related information, not procedural steps.

The following list presents some basic guidelines for working with menus:

When a menu is displayed, press the up/down arrow keys to highlight a commandname. Then press the Enter key to choose the menu command. The menu can alsobe selected by clicking with a cursor positioning device (CPD), such as a mouse.When a command ends in an ellipsis (), the application displays a dialog box thatasks the user to supply more information.

If a command turns a feature on and off, a checkmark () appears by the commandname when the feature is on.

When a command ends with an arrow ( ), the menu cascades to display morecommand names.

If a command name is grayed out, it indicates that the command does not apply to thecurrent situation or there is another selection or action before choosing the command.

Related PublicationsGE provides system instruction manuals that include publications for the differentcomponents of each product. If additional manuals are needed or for questions aboutthe publications, contact the nearest GE sales office or authorized GE salesrepresentative.

4 Chapter 1 Overview GEH-6372D GEMIS Tools for CIMPLICITY

Notes

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 2 Installation 5

Chapter 2 Installation

IntroductionWindows 95 is currently notsupported.

This chapter describes the PC and installation requirements for the products in theGEMIS Tools for CIMPLICITY. Each product is defined with specific requirementsand any additional system dependencies.

PC RequirementsIf CIMPLICITY is installed,refer to the CIMPLICITYdocumentation for therecommended hardware.

The minimum PC requirements are determined by the selected product combinationand the topology configuration of the PCs, along with the CIMPLICITY HMIproducts that were installed. If CIMPLICITY is not installed, the minimumrequirements are as follows:

DLAN+ Devcom must be NT4.0, refer to Chapter 9.

80486 100 MHz processor

Microsoft Windows NT (Windows 95 is not supported) VGA display (640 x 480 x 16 bit color or gray scale) 16 MB of RAM

Ethernet

DS6815PCLG (PCLG) assembly (required with Mode Logger option) PCA198 (ARCNET) board (required if GE DLAN+ Devcom or DLAN+ Driver

is installed ) Hard disk space (refer to the following section, Product Software for each

product description and disk space requirements) Cursor positioning device (such as a mouse) Printer (with appropriate Windows driver installed)

6 Chapter 2 Installation GEH-6372D GEMIS Tools for CIMPLICITY

Software ProductsThe following section defines products included in the GEMIS Tools forCIMPLICITY distribution and a brief description of their use. The table listsproducts that are supported on different platforms and the CIMPLICITY HMIproject required.

For more information, seeChapter 4.

Mode Logger Service interfaces with the PCLG assembly, capturing controlmessages from the DLAN+. The Mode Logger Control program must be used tomanage this function (see Chapter 4). It is installed on each PC that has a PCLGassembly and requires approximately 500 kB of disk space (see note on page 7).Message Archiver Service saves the control messages from the Mode Logger intothe Message Archiver Database. The Mode Logger Control program must be used tomanage this function. Message Archiver is installed on the same PC as the MessageArchiver Database . It requires approximately 500 kB of disk space. The MessageArchiver Database size is system dependent. It could require up to 20 MB or more ofdisk space depending on the configuration. Messages can be sent from multipleDS6815PCLG Mode Logger assemblies (PCLG) to the same Message Archiver orrun separate. However, only one Message Archiver program can be run on the samePC (see Chapter 4).

Mode Logger Control

Mode Logger Control program is the user interface to the Mode Logger andMessage Archiver services. It is installed if Mode Logger or Message Archiver isinstalled (see Chapter 4).

System DatabaseSystem Database (SDB) Utilities primarily imports selected signals from the SDBinto the CIMPLICITY Human Machine Interface (HMI) project Point Database. Thisprogram requires approximately 300kB of disk space (see Chapter 3).GE CIMPLICITY Alarm Manager Service (GECAMS) receives alarm messagesfrom the Message Archiver and submits them to CIMPLICITY HMI project AlarmManager for display and storing. The GECAMS program is started and stopped inthe CIMPLICITY HMI project. It is selected from the Project Properties dialog box(see Chapter 7).Network Time Protocol (NTP) synchronizes the PCs date and time on the networkwith a designated time Master. NTP must be installed on all PCs to be synchronizedand the PCs must be connected to Ethernet. This program requires approximately 1.2MB of disk space and must be installed on each PC (see Chapter 6).

DLAN+ Status Monitor DLAN+ Status Monitor checks the message traffic and monitors the performance ofone or more DLAN+s in the control system (see Chapter 10).DLAN+ Devcom allows a CIMPLICITY HMI project to read signals beingbroadcast and write to signals in controllers through the DLAN+ (see Chapter 9).This program is installed in a CIMPLICITY HMI project as a devicecommunications driver.

DLAN+ Driver provides driver support for the PC198 ARCNET board.


The following table lists GEMIS Tools for CIMPLICITY products that are supportedon different platforms and the CIMPLICITY HMI project required.

Product CIMPLICITYHMI Project

Windows NT DigitalALPHA

Mode Logger Service n/a Message ArchiverService

n/a

Mode Logger Control n/a System Database(SDB) Utilities

Server Node

GECAMS AlarmManager

Server Node

Network Time Protocol(NTP)

n/a

DlanView n/a Diagnostics Server or View

Node

DLAN+ Status n/a DLAN+ Devcom Server Node DLAN+ Driver n/a

Installing the ToolsFor assistance, contact:General Electric CompanyProduct Service Engineering1501 Roanoke Blvd.Salem, VA 24153-6492 USAPhone 001-540-387-7595Fax 001-540-387-8606

The program files are installed to the directory specified in the Setup program. Thesefiles include the main program and required files for the chosen product software.Help files and Release Notes are also located in this directory.

Note The Software License Agreement dialog box displays at the beginning ofset up. Please read this license and click Yes to accept all terms of the agreement.Refer to the following section Software License Agreement.

Refer to the following sectionLicense Agreement.

Note This installation requires the SDB version V03.02.00C or later. Verify thisversion by choosing About the SDB utility from the SDB Utility Help menu. Duringsetup, a Question dialog box displays to confirm this version.

The product software can be installed from disks or from a network drive.

Make sure that all programs are stopped. The tool installationincludes drivers that could be in use by other applications.

CAUTION


To install from disks.

Type b:\setup if installingfrom the b drive.

1. Place Disk 1 in the disk drive.

2. In Windows NT 3.51, from the Program Managers File menu, choose Run. Or

In Windows NT 4.0, click Start button and click on Run. The Rundialog box displays. Type a:\setup and click OK.

3. Follow the setup instructions from each screen to install the remaining disks.

To install from a network1. From File Manager (3.51) or Explorer (4.0) locate the appropriate network

drive that contains the GEMIS Tools for CIMPLICITY.

2. Locate the directory for the tools and disk 1.3. Double-click disk 1 and then double-click setup.exe. The setup process

automatically starts.

4. Follow the setup instructions from each screen.

The example and setup screens in this manual do not reflect the actual applicationconfigurations. Be sure to follow the correct setup procedures for your application.

License AgreementThe following Software License Agreement dialog box displays during installation.This license agreement must be read and agreed to before the installation can becontinued. Click YES to continue, click NO to exit the installation.

CAUTION


The Product License dialog box displays to enter the license number beforeinstallation will continue. This number can be found on the disk label. Enter thenumber in the format as indicated.

A dialog box displays to indicate the minimum version of the SDB Server requiredby one or more products in this distribution.


Products InstalledWhen setup runs, the product selection screen displays. Choose the desiredproducts to be installed from the following list:

If CIMPLICITY is upgraded,GECAMS and DLAN+Devcom must be reinstalled.

Mode Logger

Message Archiver

Network Time Protocol

DlanView

Diagnostics

DLAN+ Status

SDB Utility (CIMPLICITY Server required) GECAMS Alarm Manager (CIMPLICITY Server required) DLAN+ Devcom with Driver (CIMPLICITY Server required) DLAN+ Driver only

Click beside the productname. A check () displaysbeside the product to install.

Click Next to start the installation.Setup installs the products to a default Destination Directory.


Choose Next or click Browse to choose a different directory.Setup creates the Program Folder: GEMIS Tools for CIMPLICITY to group allproduct icons that were chosen to install. If desired, type a new folder name orchoose one from the Existing Folders: list as shown in the following screen.

Setup automatically continues to load the program files. The Information dialog boxinforms when the installation is complete. When setup has completed, all necessaryfiles are copied to the destination product directory along with any supporting filesand databases required for proper program operation.


SDB InformationSeveral products require the SDB Server. It provides tools to import/export andverify data to and from the CIMPLICITY HMI project Point Database. The SDBInformation dialog box displays to specify the SDB location (refer to Chapter 3).Enter the SDB Host and SDB Path and click Next.

Uninstall ProgramsThe uninstall feature is used to remove a product from the system. All files and othercomponents are removed completely from the system.

Note NTP, Mode Logger, Message Archiver, and DLAN+ Driver cannot beremoved using Uninstall. These products must be uninstalled by running the setupdisk used to install the products. Then, choose the product from the dialog box. Aprompt displays to choose upgrade or remove the selected products.

To uninstall a productIn Windows NT 3.51, from theGEMIS Tools forCIMPLICITY ProgramGroup, choose the desiredUninstall icon.

1. Click Windows Start button, Settings and click Control Panel.2. From the Control Panel dialog box, double-click on Add/Remove

Programs. The Add/Remove Program Properties dialog box displays.3. Click on the tab Install/Uninstall.4. From the list, click the desired program and click the Add/Remove button.5. The Confirm File Deletion dialog box is displayed. Click on Yes.


All program components are automatically removed. The following screen displaysto show the removal progress. When Uninstall is complete, click on OK.

Upgrading From an Earlier VersionThis manual describes functions found in version V03.04.00C of the GEMIS Toolsfor CIMPLICITY. To upgrade to this version, additional product upgrades may berequired to guarantee product compatibility. The following table lists products andthe minimum required version to maintain compatibility in the system. Refer tothe respective product documentation for additional dependencies within eachproduct.

Product Order Number Publication # Version V03GEMIS Tools forCIMPLICITY

DS206GT4C0304 GEH-6372 V03.04.00C

System Database(SDB)

DS206DXDB GEI-100189 V03.02.07C

GE Control SystemToolbox

DS206TBOX GEH-6333 V03.02.00C

Note If upgrading from CIMPLICITY HMI 3.0 to version 3.1, refer to theCIMPLICITY HMI documentation and reinstall GEMIS Tools for CIMPLICITY.Some products in the tools will not run unless they are reinstalled after installingCIMPLICITY HMI.


Notes

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 3 System Database (SDB) Utilities 15

Chapter 3 System Database (SDB) Utilities

IntroductionThe SDB Utilities must run onthe PC that is theCIMPLICITY Server.

The CIMPLICITY HMIProduct must be installedbefore this application can beused.

.csv and .snf are text files.

The System Database (SDB) Utilities provide a bridge between the CIMPLICITYHMI Project and the SDB database. The SDB Utilities support four sources forimporting signal and alarm data into the CIMPLICITY HMI Project as follows: Signals from the SDB. The SDB contains data (primarily signals) that is used by

one or more devices in the system. Signals available for import into theCIMPLIITY Project must be posted to the SDB from the Ethernet or DLAN+page of a device.

Signals from a comma separated variable (*.csv) file. A .csv is a commonoutput format for spread sheet and database files. Each line is a signal in thisapplication.

Signals from a shared name file (*.snf). Each Series 90-70 programmable logiccontroller (PLC) program has a *.snf associated with it that contains all of thesignals used in the PLC.

Alarms imported from the SDB into the CIMPLICITY HMI Project alarmdefinitions.

Note For more information, refer to Appendix B and GE Fanuc Automation andCIMPLICITY HMI products documentation.

16 Chapter 3 System Database (SDB) Utilities GEH-6372D GEMIS Tools for CIMPLICITY

ConceptsConfiguration data is saved toa db_utils.cfg.

The SDB Utility must be configured before signals and alarms can be imported fromthe SDB to the CIMPLICITY HMI Project. When the SDB Utility is started, theWork Area window displays four configuration items as follows:

CIMPLICITY Project is the name and location of the CIMPLICITY HMI projectfile (.gef).CIMPLICITY Server contains the topology information for the CIMPLICITY HMIPC, which is posted to the SDB database. This includes the name (as a device namein the SDB) of the CIMPLICITY HMI PC and the network(s) connected to it.SDB Server is the name of the PC that contains the SDB Server and the location ofthe SDB database.

Resource List is a list of Resources used to filter SDB signals when importing. Animport can include one or multiple Resources.

Note These configuration items are defined in the section Configuration.

The following diagram shows these configuration items in relation to a CIMPLICITYHMI project.

Ethernet

Alarm_HelpArcDataLock

LogMasterScreensScripts

*.GEF

ProjectCIMPLICITY HMI

CIMPLICITY ServerDevice

SDB Server

System Database (SDB)

Resource_AResource_B

(Items for SDB Work Areaare in bold and italics.)


Using SDB Utilities To start the SDB Utilitiesw From the Program Manager, choose the GEMIS Tools for CIMPLICITY

program group/folder, and click SDB Utilities icon.The SDB Utilities window displays.

SDB UTILITYWORK AREA

LOG WINDOW

MENUCOMMANDS

STATUS BAR

SDB Utility MenusFile MenuThe File menu provides the following commands:

Open CIMPLICITY Project allows the user to open a CIMPLICITY HMI project(.gef).Save CIMPLICITY Project allow the user to save SDB Utility configuration datain a db_util.cfg file located in the CIMPLICITY HMI projects data subdirectory.


Edit MenuThe Edit menu provides commands to add to or change the SDB Utilityconfiguration.

Edit Device is used to change the five character device name and TCP\IP name as itis listed in the SDB for the CIMPLICITY HMI Server PC.

Edit Net is used to change the name and type of Selected network(s) connected tothe CIMPLICITY HMI Server.

Delete Net removes the Selected network connection from the CIMPLICITY HMIServer.

Insert Net is used to add a network connection to the CIMPLICITY HMI Server.

Select Resources is used to change the list of Resources. Resources filter SDBSignals when importing.

View MenuThe View menu provides commands to view log files and other view commands asfollows:

Toolbar toggles to display or hide the toolbar.Status Bar toggles to display or hide the Status Bar.

Refer to the document SDBBrowser, GEI-100271.

SDB Browse starts the SDB Browser to view signals and other data in the SDB.Utility Log File displays the SDB Utilities Log file through Notepad. This log filecontains data such as import and export errors. Use the scroll bar orPageup/PageDown to view the entire file.

For example, the file can benamed IExxx.log, where xxxis a number.

CLIE Log File allows the user to view a command line import/export (CLIE) logfile through Notepad. The log file is created and named when an import or export isperformed. The log file name displays in the Log window. Use the file name tochoose the file to view from the SDB Utility Log file.

Clear Log Window removes all text from the Log window


Tools MenuThe Tools menu provides commands to import or export data between theCIMPLICITY HMI project, the SDB database, and the SDB Utility configuration.

The Registry is the WindowsNT database repository forinformation about acomputers configuration.

Import reads signals and alarms from the SDB database and places them into theCIMPLICITY HMI project (see Tools/Import command below).Export reads signals (points) from the CIMPLICITY HMI Point Database andwrites it to a .csv file. Routing tables (.rte files) for a DLAN+ card are also producedthrough the export menu (see Tools/Export command below).Verify compares the contents of the CIMPLICITY HMI Point Database and thesignal table in the SDB (see Tools/Verify command below).Post to SDB stores the CIMPLICITY HMI Server topology (Server name andnetwork connections) into the SDB.ConfigDlan writes DLAN+ board configuration data to the Registry based on theCIMPLICITY HMI Server topology. Board(s) are installed before or after runningconfigDlan. However, if the DLAN+ board is installed after running configDlan, itmust be run again to obtain the correct configuration data into the Registry.

Tools/Import CommandThe Import command allows the user to import signals (points) into theCIMPLICITY HMI Point Database or alarms into the CIMPLICITY HMI projectAlarm definitions.

Import/Points/SDB-All imports signals (points) from the SDB from all devices onthe Selected network that belong to any of the Resources in the Resource List.

Import/Points/SDB-Device imports signals (points) from the SDB from aSelected device on the Selected network that belong to any of the Resources in theResource list.

Import/Points/Select Resources is used to edit the list of Resources, which areused to filter SDB Signals when importing.

Import/Points/CSV File imports signals from the selected .csv or .snf file.Import/Alarms imports alarms from the SDB into the CIMPLICITY HMI projectalarm configuration.


Tools/Export CommandsThe Export commands allows the user to export selected data to text files.

Export/Point Database exports all points from the CIMPLICITY HMI projectPoint Database to a selected .csv file.

Export/Route Table exports DLAN+ routing information to a text file(s) used bythe DLAN+ Devcom.

Tools/Verify CommandsThe Verify commands allows the user to compare signals (points) between the SDBand the CIMPLICITY HMI Point Database. The result includes the points that aredifferent and indicates which points are in the Point Database and not in the SDB.Extra points in the Point Database need to be deleted to make the SDB and PointDatabase match.

Verify/All Points compares SDB signals from all devices on the Selected networkthat belong to any of the Resources in the Resource list.

Verify/SDB-Device compares SDB signals from a Selected device on the Selectednetwork that belong to any of the Resources in the Resource list.

Options MenuThe Options menu allows the user to determine if scale factors or alarm data areimported from the SDB when points are imported.

Point Data allows the user to choose scale or alarm data when importing signals.Select SDB allows the user to choose the SDB Server and location of the SDBdatabase.


Windows & Help MenusThe Windows and Help menus have the same commands as standard Windows-basedsoftware. The Windows menu controls how the windows are displayed on the screen.The Help menu contains the current revision number and starts the online Helpapplication.

ConfigurationThese items are displayed inthe Work Area when the SDBUtility is started (see page16).

The Resource List is onlyrequired to import signals,not for importing alarms.

The SDB Utility must be configured before it can import signals and alarms into theCIMPLICITY HMI Project. The configuration consists of four major items: CIMPLICITY HMI Project CIMPLICITY Server (topology) SDB Server

Resource List

CIMPLICITY HMI ProjectCIMPLICITY HMI Project isthe first item in the WorkArea.

When configuring the SDB Utility, a CIMPLICITY Project must be chosen first. TheSDB Utility always starts with the last opened CIMPLICITY Project. Choose aproject after installation or change a project as follows:

To select A CIMPLICITY HMI Project

Or click on .

Click on to save the file.The example file would besaved to a file calleddb_util.cfg located in theCIMPLICITY Projects datasubdirectory (such as\Cimplicity\Projects\drsTest\data\db_util.cfg).

1. From the File menu, choose Open Project.2. From the Open dialog box, choose the desired .gef file from the project

directory. This example shows the location as CIMPLICITY\Project\drsTest.


CIMPLICITY Server (topology)In order for signal to imports correctly, the CIMPLICITY Server PC name andnetwork connections must be configured and posted to the SDB database. Then, theydisplay in the Work Area topology, as shown below:

To configure the CIMPLICITY Server

If the TCP\IP name is leftblank, the Device Name isused when posting to theSDB.

1. From the Edit menu, choose Edit Device. The Device dialog box displays.2. Enter a user-defined Device Name (up to five character name for the server).3. Enter the PCs TCP/IP Name (up to 12 characters and optional), and a

Description (optional).

4. Click OK. (These names display in the Work Area).5. Add a network connection for the CIMPLICITY Server device. From the Edit

menu, choose Insert Net.


The Edit NET connection dialog box displays.

6. Enter the Net Name7. Enter the Net Type. Choose from two network types, DLAN+ (drive network)

and Ethernet Service Request Transfer Protocol, (ETHR_SRTP).

Note: If the networks were previously defined in the SDB (through other devices),then the name must be spelled correctly. Otherwise, a new network is added to thedatabase when posting occurs. The network name is NOT case sensitive.

ETHR_SRTPIf an Ethernet network is used, only a network name and type shown in the previousdialog box is required. However, if DLAN+ is used, additional fields display andmust be defined.

DLAN+ Net Type To configure a DLAN+ connection1. From the Edit NET connection dialog box, in the Net Type text box, choose

DLAN+.2. Enter the fields as follows:

Drop Number is the DLAN+ (ARCNET) drop number. It must be between 1 and255. If this number is left zero, the SDB Server assigns an available drop afterposting to the SDB. The DLAN+ card must be configured with the same dropnumber.


Card Number is the DLAN+ card number for this network connection. This drop-down list displays the card(s) that was installed with DLAN+ Devcom (see Chapter9). DLAN+ Devcom installs and numbers up to four cards. Choose the card numberthat matches the DLAN+ name and drop number.

Use -1 if the DLAN+ Devcomis not installed yet.

Page Number is the DLAN+ page number. It must be between 1 and 255. If it isleft at zero (default) the SDB Server assigns an available page after posting to theSDB.

Record DLAN+ Data to RegistryThe DLAN+ drop number, page number, and net name must be recorded to theRegistry. This data is read by the DLAN+ Devcom to configure the PC198 board,when the PC is booted (see Chapter 9). To record the DLAN+ data in the registry1. Enter data for the chosen DLAN+ in the DLAN+ Edit NET connection dialog

box.

2. From the Tools menu, choose the command ConfigDlan.

When the SDB Utility is started, it compares its topology to the registry data . If thedata does not match or there is no registry information, the SDB Utility displays anote in the Log window as shown in the following screen:


Edit or Delete a Network Connection To edit or detete a network connection

Click on to expand items inthe Work Area.

1. From the SDB Utility Work Area, expand the item CIMPLICITY Server andthen expand Net Connections.

2. Click on the network to edit/delete.

3. From the Edit menu, choose Edit Net.or Delete Net

Every time the CIMPLICITY Server topology is edited, perform the following steps:

1. Save project configuration (File menu/Save Project).2. Post to the SDB (Tools menu/Post to SDB).3. Configure the network device (Edit menu/Edit Device or Edit Net.)4. If a DLAN+, record to registry (Tools menu/ ConfigDLAN)


SDB ServerTo perform most tasks within the SDB Utility, the SDB Server PC name and SDBdatabase location must be defined. If these locations are specified during installationof the GEMIS Tools for CIMPLICITY, the data is stored in the registry and used toset the SDB Server name and database location.

Note If the user changes the SDB Server name and database location through theSDB Utility, then the registry data is also updated.

To specify or change the SDB Server1. From the Options menu, choose Select SDB. The Database dialog box

displays.

2. Enter the name and path as described below.

Server is the name of the PC where the SDB Server is located.Name is the fully qualified path (subdirectory) where the SDB database is located

Note The drive specification (in this example c:) is from the perspective of the SDBServer PC itself. The c: drive on computer pdntsql does NOT need to be mapped tothe file system for the CIMPLICITY PC.

Click on to expand SDBServer.

To display the SDB Server name and locationw From the Work Area, expand the item, SDB Server. The SDB Server and SDB

Name that was entered in the dialog box above display in the Work Area asfollows:


Resource ListIn the GE Control System Toolbox, network signals can be associated with aResource. The Resource name is used by the SDB Utility to filter the signals (points)imported into the CIMPLICITY HMI Point Database. The Resource List containsselected resources for signal import.

To edit the Resource ListThe Resources that are usedas a filter in the SDB Utilityfor importing signals into thePoint Database must also bedefined as Resources in theCIMPLICITY HMI project.For example, in the SDBResource dialog box, theSelected resource of ENTRYand HYDR must be defined asResources in theCIMPLICITY HMI project. Ifthey are not, then any signalsassociated with these tworesources will fail to import.

1. From the Edit menu, choose Select Resources. The SDB Resources dialogbox is displayed. The Resource List is obtained from the SDB anytime this dialogbox is invoked.

2. Use the Add-> and


Exporting Routing Tables

A routing table is requiredeven if only one DLAN+ isconnected to the HMI Server.

Routing tables are used by the DLAN+ Devcom device driver to properly routeStatus_S command signals to the correct device. The routing tables are text files (.rte)that correlate the devices in the system with the drop number used to get a commandmessage to that device. Every DLAN+ attached to the CIMPLICITY HMI Server hasa corresponding .rte file. Refer to Appendix B for an example of a routing table textfile.

To export routing tablesw From the Tools menu, choose Export and Route Table.

The SDB Utilities reads the required data from the SDB database and writes the .rtefiles to a standard location. If the GEMIS Tools for CIMPLICITY are installed in thedefault location (C:\GEMIS-MMI), then routing tables are located in the subdirectoryC:\GEMIS-MMI\support\. The routing table file name would take the form of:

_.rte

The routing table files are now available to the applications that need them. In thefollowing screen, the device name for the CIMPLICITY Server is CHMI and thenetwork name is DLAN. The routing table file name is CHMI_DLAN.rte and islocated in the subdirectory C:\GEMIS-MMI\support\. The Log window displays theresults of the export of routing table.


Importing Signals and AlarmsThe SDB Utility can alsoexport the CIMPLICITY HMIPoint Database to a .csv or.snf text file.

The main purpose of the SDB Utility is to import data from the SDB database to aCIMPLICITY HMI Project. This data includes: Signals (points) Alarms

SDB Signals (Points)All imports are filtered by theResource List. Only signalsassociated with one of theSelected resources will beimported.

Signals in the SDB database can be imported into the CIMPLICITY HMI ProjectsPoint Database. These signals are chosen by the user from a network or device on thenetwork. The user can chose:

Import all signals on the selected network.

Import all signals owned by a device on the selected network.

Note If the CIMPLICITY Server is connected to two networks, then two importsare required to receive signals from both networks into the CIMPLICITY HMI PointDatabase.

The following diagram shows data imported form the SDB to CIMPLICITY HMIPoint Database.

SDB ImportSystem

Database(SDB)

CIMPLICITY HMIProject Point

Database

Selected SignalGroups

Ethernet

*.csv File

CLIE Import of *.CSVFile

Must be in same PC

Optionally over Ethernet

SDB_IMP.vsd


Whether importing for a single device, or importing for all devices on a network,there are two steps, which occur automatically:

1. Selected signal data is copied from the SDB database into an intermediate .csvfile.

2. A CLIE import command is executed that references the intermediate .csv file.

Note Refer to Appendix B for more information on how signal data is mapped fromthe SDB to the CIMPLICITY HMI Point Database when an import is performed bythe SDB Utility.

Import Device Point OptionsSignals (points) in the SDB database can be associated with a scale factor and alarmattributes. The following dialog box is used to control whether a signals scale andalarm data are imported to the CIMPLICITY HMI Point Database.

To choose import point options1. From the Options menu, click on Point Data. The Import Device Point

Options dialog box displays.


2. Choose from the following options.

If this box is not checked, thepoint is imported withconversion type NONE.

Include Scales imports the point with a CIMPLICITY HMI conversion type(CONV_TYPE) set to CC for Custom Conversion, if the signals have a scalesassociated with them. The conversion equations are determined as follows:

eng_max, eng_min, src_max, and src_min are the SDB Conversion factors for thesignals scale.

m = (eng_max - eng_min)/(src_max - src_min)b = (eng_min - src_min * m)

For more information, referto the CIMPLICITY HMIdocumentation.

forward equation = (%p/m + b)reverse equation = ((%p - b)*m)CIMPLICITY Point Conversion Limits are not set. The CIMPLICITY HMI Pointdisplay limits are populated with the SDB entry limits.

If this box is not checked,alarm data is not importedinto the Point Database.

Include Alarm Data imports alarm data into the CIMPLICITY HMI system alongwith the points, if signals have alarm data associated with them (through a scale). Themapping of data between SDB and CIMPLICITY HMI is as follows:

SDB (Scale) CIMPLICITY HMI DescriptionHHIGH ALM_HIGH_2 High alarm limitHIGH ALM_HIGH_1 High warning limitLOW ALM_LOW_2 Low alarm limitLLOW ALM_HIGH_1 Low warning limit

If this box is not checked, butalarm data is imported, thenthe alarm and message arenot defined for the point.

Include Alarm Class and Msg: uses the default alarm class when signals withalarm data are imported in the CIMPLICITY HMI Point Database. The alarm classname must already be defined in the CIMPLICITY HMI system for the signals toimport successfully. The signal description is used as the default alarm message.

Note The Include Alarm Class and Msg: is grayed out if the Include AlarmData option is not checked.


Import Signals (Points) To import points1. From the Tools menu, choose Import, and choose Points.2. Choose SDB-Device to import points from a specific device for a given

network or choose SDB-ALL to import points from all devices in a network.

The Select Net dialog box displays for either choice.3. Choose the desired network that contains the points to import, and click OK.

SDB - All imports point from all devices in the selected network (see step 5).

4. If Import/Points/SDB-Device is chosen, the Select Device dialog boxdisplays. Choose the device to import points from (this list of devices includesonly those connected to the network chosen in Select Net).

The Log window also displayserror messages.

5. Click OK. The import process runs to completion. The Log window will recordthe SDB Utilitys response to import the points.


The following is an example Log window:

.csv File To import points from a .csv file1. From the Tools menu, choose Import, and choose Points.2. Choose .CSV File. The standard Open file dialog box appears.3. Choose a .csv file. The CLIE Import Options dialog box displays.


The clie import options define a set of actions for every imported point in the .csvfile as follows:

Device (-D) allows the user to enter a DEVICE_ID name to associate with everypoint in the .csv file, which do not have a DEVICE_ID defined. The DEVICE_ID inthis text box must be a valid DEVICE_ID in the CIMPLICITY HMI project. (-D isthe command line option indicator, if CLIE is used in a command shell).

Resource (-R) allows the user to enter a RESOURCE _ID name to associate withevery point in the .csv file, which do not have a RESOURCE _ID defined. TheRESOURCE _ID in the text box must be a valid RESOURCE _ID in theCIMPLICITY HMI project. (-R is the command line option indicator, if CLIE isused in a command shell).

Prefix (-Pa) allows the user to enter a prefix for the beginning of every POINT_IDin the .csv file. The Prefix plus the POINT_IDs must not be more than 32 characters.(-Pa is the command line option indicator, if CLIE is used in a command shell).

Import AlarmsThere are two types of alarms in the SDB Utility (both require DLAN+): Broadcast Alarms (user-defined) Standard Device Alarms

Broadcast AlarmsUser defined Broadcast Alarms are defined in the GE Control System Toolbox,System Device. The System Device posts (adds) the alarms to the SDB database,where they are stored. The name of a Broadcast alarm is created from two parts: a 3-character Alarm group name and the alarm number for the group. For example,Hydraulic pressure low alarm can be named HYD4. HYD is the group name and 4 isthe alarm number for the pressure low alarm.

UC2000 Alarm_Xmit blocks use these defined alarm names to specify the alarms tobroadcast on the DLAN+ when the state of the system indicates the alarm condition.For example, the UC2000 monitors an I/O input, Hydraulic pressure. When thepressure gets below a pre-configured level, an Alarm_Xmit block sends AlarmHYD4. The Mode Logger receives this message, fills in any substitution variables,and then sends it to the CIMPLICITY HMI Alarm system.


In order for the CIMPLICITY HMI Alarm system to display the correct message, theBroadcast alarm definition must be imported from the SDB and put into theCIMPLICITY HMI Alarm definition database.

The following figure defines the Broadcast Alarm process.

GEMIS Control System Toolbox

System_Device_1Scale_DefNet_Names

Broadcast Alarms

Alarm_1Alarm_2Alarm_3

Type_DefResource

Group_A

Alarm_XMITAlarm_XMIT

System Device

UC2000 Device

SDB

Ethernet

CIMPLICITYHMI

Server

Posting of alarm definition toSDB for import toCIMPLICITY alarm definitionand access to MessageArchiver in run time.

Alarm_1Alarm_2Alarm_3

Group_B

BinaryFormat

ALARMDEF.DATAlarm Import intoCIMPLICITY HMI

Project

1. Define broadcast Alarm using the System Device. Postto the SDB.

2. In the UC2000, define the Alarm _XMIT block to usethe Broadcast Alarm definition (refer to GEH-6333B).

3. Use the SDB Utility to import alarm definitions from theSDB into CIMPLICITY HMI.

Standard Device AlarmsEach device connected to the DLAN+ can send (broadcast) standard faultmessages. These are pre-configured standard messages that the system designer doesnot have to configure.


A device can send two types of standard fault messages:

Fault messages announce that something is wrong, but the device continues torun.

Trip messages are faults that cause the drive or device to trip fault (stop).When Standard Device alarms are imported into the CIMPLICITY HMI Alarmsystem, two alarms are produced for every device on any DLAN+:

DEVNAME_TRP

DEVNAME_FLT.

The names for these alarms are derived from the devices name. For example, the twostandard alarm messages for a device called POR1 (Payoff Reel 1) will bePOR1_FLT and POR1_TRP. When the device sends the actual message, the contentof the message describes the actual fault, such as:POR1_TRP-message = fault #23, the drive has had an overspeedfault

Note Refer to Appendix B for mapping between SDB Broadcast Alarms andCIMPLICITY HMI Alarms.


Importing SDB AlarmsBroadcast Alarms in the SDB can be imported into the CIMPLICITY HMI Projectsalarm table through the Alarm Import Options dialog box. This procedure can alsoimport Standard Device Alarms into the CIMPLICITY HMI Project. Both types ofalarms require DLAN+.

To import Broadcast and Standard Device alarms1. From the Tools menu, choose Import, and choose Alarms. The Alarm

Import Options dialog box displays.

2. Choose from the following options:

Broadcast Alarms can be checked to import all user-defined Broadcast alarms.Standard Device Alarms can be checked to import standard alarms based on thedevices connected to DLAN+.

Add Undefined Alarm Classes can be checked to add Broadcast or StandardDevice alarms that have an Alarm class, not defined in the CIMPLICITY HMIproject (the alarm class will be added). If the box is not checked and undefinedAlarm Classes are referenced, then those imported alarms will fail to validate.

3. Click Import Now to start the import process.The import actions are displayed in the Log window, including fault messages.


Notes

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 4 Mode Logger 39

Chapter 4 Mode Logger

IntroductionThis chapter describes the Mode Logger system. The Mode Logger and MessageArchiver Services read and save messages transmitted on DLAN+. These messagescan be viewed with DlanView (see Chapter 5). The Mode Logger Control applicationmanages the Mode Logger and Message Archive Services. It is installed as part ofthe Mode Logger and Message Archiver Services.

ConceptsMode Logger and MessageArchiver are implemented asWindows NT services. Theyare started and stopped by theWindows NT ServiceManager. The user controlsthe services indirectly with theMode Logger Controlapplication, which writesconfiguration data into theWindows NT registry andsends command to theWindows NT ServiceManager.

The Mode Logger service reads raw messages on the DLAN+ and sends them to theMessage Archiver. The Message Archiver translates the messages, using informationread from the System Database (SDB) and writes them to the Message ArchiverDatabase.

GECAMS provides a connection to the CIMPLICITY HMI Alarm Manager RuntimeProcess (AMRP) from the Message Archiver. Using this interface, the MessageArchiver can send DLAN+ alarm messages to CIMPLICITY, where they can beviewed with the CIMPLICITY HMI Alarm Viewer (AMV) and optionally loggedinto the CIMPLICITY HMI Alarm/Event Database.

DlanView can display the DLAN+ messages recorded in the Message ArchiverDatabase. The Fault Text Database contains the text messages corresponding to thefault codes and device types transmitted on DLAN+.

40 Chapter 4 Mode Logger GEH-6372D GEMIS Tools for CIMPLICITY

The following diagram displays the data flow in the Mode Logger system.

ModeLoggerPC 1

MessageArchiver

Database

MessageArchiver

DLAN+ Messages

CimReport

DLAN+Messages

DLAN+ Network A

SDB

CIMPLICITYAlarm/Event

Database

* Selected message types

PCLG Assembly

Signal Names in DLAN+ Message


Within a single PC

Alarm ManagerInterface

CIMPLICITY Alarm API

CIMPLICITYAlarm Mgr(AMRP)

AlarmView

ModeLoggerPC 2

* Device faults and process alarmstransmitted by DLAN+ devices

CIMPLICITY HMI Project

DLAN+ Network B

PCLG Assembly

The proper display of messages from different DLAN+s depend on thetwo Mode Logger PCs having the same time. If the two PCs differsignificantly, messages from one DLAN+ always appears at the top ofthe display, since they are sorted by time. If the time difference is largeenough, the entire display may consist of messages from one DLAN,giving the impression that no messages at all are being sent on the otherDLAN. For more information, refer to Chapter 6, Network TimeProtocol.

Mode Logger (Modelogr.exe)To install Mode Logger,choose it from the product listduring installation (seeChapter 2).

The Mode Logger service must be installed and run on the same PC as theDS6815PCLG Mode Logger assembly (PCLG). Runtime parameters for the PCLGassembly and Mode Logger are stored in the Windows NT registry. When executed,it reads the registry and performs the following:

Maps the area of host computer memory shared with the PCLG.

Checks for the presence of a properly configured PCLG by finding a validsignature in the shared memory.

Downloads the firmware into the PCLG and sends the start command.

Periodically, checks the shared memory for incoming messages, reads messagesinto a buffer and sends them to the Message Archiver.

CAUTION


Message Archiver (MsgArchiver.exe)The Message Archiver program can be installed on the same PC as the Mode Loggeror any PC that can communicate with the Mode Logger PC through TCP/IP.Message Archiver receives messages from Mode Logger, translates the raw messagesinto text strings, and writes them into the Message Archiver Database to be viewedby DlanView or the Control System Toolbox.

Fault Text DatabaseThe Fault Text Database provides information for a specific fault code and devicetype. It is used by Message Archiver at runtime to translate fault codes into thecorrect text messages. The device types include:

AC2000 Digital Adjustable Speed Drive (AC2000) DC2000 Digital Adjustable Speed Drive (DC2000) EX2000 Digital Exciter (EX2000) Operator Console (OC2000) Unit Controller (UC2000) Series 90-70 Programmable Logic Controller (PLC)

Note If a device is updated independently on a process or customer site, new faulttext messages will not be available to the Message Archiver. It is necessary to updateMode Logger to the most recent release.

Message Archiver DatabaseThe Message Archiver Database contains all translated DLAN+ messages and alarmsfrom the Message Archiver. The database is updated periodically. To save adatabase for later analysis, copy the file to a new location. Use DlanView to view thesaved file.


ConfigurationThe Mode Logger System Control is used to set up the Mode Logger and MessageArchiver services.

To start the Mode Logger Control applicationw From the GEMIS Tools for CIMPLICITY program group/folder, click

the Mode Logger Control icon. The Mode Logger System Control window is displayed.

The Mode Logger System Control window allows the user to start and stop the twoprograms that make up the Mode Logger system. The programs are:

Mode Logger (PCLG assembly) Message Archiver

If one of these (or both) programs are not installed, its status in the Mode LoggerSystem Control window under Currently will be Not Installed. It will not bepossible to configure or start that program. After installation and the initial setup, theprograms can be started automatically when Windows NT first starts up as follows:

To set up the Mode Logger or Message Archiver for start up1. From the Mode Logger System Control window (shown above), click

Settings The Mode Logger Settings dialog box is displayed. It contains a tab for the

Mode Logger and the Message Archiver program.

2. Choose a startup mode for each program (choose Automatic, Manual, orDisabled).


Mode Logger SettingsThe Mode Logger tab is set as follows:

DLAN+ Net Number identifies the DLAN+ that the PCLG is connected to asdefined in the SDB. The default is one.

Process rate is the rate the host program empties the DLAN+ message buffers inthe shared memory of the PCLG assembly. If the number is too small, the hostprogram uses excessive CPU time checking these buffers unnecessarily. If thenumber is too large, the buffer can fill and overflow before the host program cancheck and data will be lost. The default rate is 250.

Message Archiver Location is the PC which hosts the Message Archiverprogram. Mode Logger messages are sent to the Message Archiver either on ThisPC (local host) or Remote PC (through TCP/IP).Startup Mode controls how the Mode Logger program is started. In most cases, itshould be set to Automatic.


Message Archiver SettingsThe Message Archive tab is set as follows:

Allow a larger messagedatabase for troubleshootinga system problem.

Limit size of message database allows the user to enter a maximum number ofrecords. Once the maximum number of records is reached, the oldest records areoverwritten by newer messages. The limit depends on the size of the hard drive andthe requirements of other programs.

SDB Location is the Server Name and Path directory for the SDB. If the SDB ison the same PC as Message Archiver, enter localhost. The Message Archiver usesthe SDB to translate the device IDs, drop numbers, word offsets, and such into deviceand signal names.

Startup mode in the Message Archiver is automatic when the PC is rebooted.However, if Mode Logger messages are directed to a Message Archiver on adifferent PC, set the startup mode to manual, or disabled, to avoid unnecessary use ofsystem resources.


If the CIMPLICITY HMI Alarm Manager is available in the system, check the boxSend GE DLAN+ alarm messages to CIMPLICITY Alarm Manager. Thefollowing field displays under Interface to CIMPLICITY.

Refer to Chapter 7, AlarmManager Service.

CIMPLICITY Server node identifies the server PC. The Alarm Manager Interfaceprogram must run on the CIMPLICITY Server. If the current PC is not theCIMPLICITY Server, choose Remote PC option button and enter the name of thePC that is the CIMPLICITY Server node.

PCLG AssemblyMode Logger communicateswith the SDB Server, MessageArchiver and CIMPLICITYHMI Alarm Manager usingTCP/IP.

Mode Logger program reads raw DLAN+ messages through the DS6815PCLG ModeLogger board (PCLG) assembly and sends them to the Message Archiver program.The Message Archiver decodes these messages using data from the SDB and storesthe resulting text messages in the Message Archiver Database. If CIMPLICITY HMIis available, the device fault and other alarms received on the DLAN+ can also besent to the CIMPLICITY HMI Alarm Manager for display and storage. DlanViewreads, sorts, and displays the messages from the Message Archiver Database. Refer tothe figure on page 50.


SettingsThe PCLG assembly holds the daughter board DS6800CCIE (CCIE).

J6 J5

J3 J4 J7

SW 1

CCIE DAUGHTER BOARD

8 7 6 5 4 3 2 1

OPEN

LEDs

Set the PCLG Assembly as follows:

1. Check the switches and jumpers on the PCLG as follows:SW 1 1-7 are CLOSED and 8 is OPEN -select shared memory location

0xD0000J6 Jumper right two pins (LOG)J5 Install jumper on both pinsJ3 Remove jumper, no CPU addressJ4 Remove jumper, no CPU interruptJ7 Install jumper on ISA position

The flickering light indicatesthat there is activity on thenetwork.

2. Install the PCLG in the PC and connect the DLAN+ cable. Leave the top of thePC open, so that the light-emitting diodes (LED)s are visible.

3. Start up the PC. The yellow LED should begin to blink steadily, about twice persecond. If it doesnt, the board is bad. If it does blink, install the Mode Loggerprograms.

4. Check the settings for Mode Logger (see Chapter 4) and start it up. The yellowLED on the PCLG may light solid for a time, then flash twice per second for awhile. Eventually the light should begin to flicker intermittently.

If the LED(s) are out and the cable is connected, check for one of the following: PCLG may be bad

DLAN+ cable may not be connected to a valid DLAN+

Problem with the BIOS


Memory Conflicts and BIOS ProblemsThe PCLG communicates with the PC host through shared RAM. Anything thatinterferes with this memory can cause problems. In particular, if a device such as anSCSI adapter or a network card is configured to 0xD0000, or 0xD8000 or anyaddress in the D segment, the PCLG or the competing device may not work.

A device driver, MapMem is installed with Mode Logger to provide the interface tothe shared memory on the PCLG assembly. MapMem attempts to map a section ofthe PCs memory to the PCLG memory. If another device has already mapped thismemory, MapMem fails and Mode Logger does not run.

To check for conflicts1. From Windows NT (Version 4.0), Programs, choose Administrative

Tools.2. Choose Windows NT Diagnostics and the tab Resources.

3. Click on button. If Mode Logger is installed, the following linedisplays:

000D0000 - 000DFFFF MapMem 0 Isa

If any part of the address range is mapped by some other device, MapMem will notstart, and Mode Logger will not run. If the competing device cannot be configured touse some other memory location, then either that device or the PCLG must be movedto another PC.

Problems can occur if 0xD0000 addresses are selected for shadowing in the BIOS.BIOS problems are characterized by the failure of the Mode Logger program tocommunicate with the PCLG assembly.

Revision should be 4.05.1.1awith SCSI V.1.2 or later.

Note There is a known problem with some BIOS revisions for TMI P166(P5000HX) systems. Obtain an updated revision by downloading the files from theTMI web site http://www.texmicro.com.

Mode Logger errors are written to the Windows NT Event Log.

To view error messagesMessages indicating that thePCLG is active and capturingmessages most likely meanthat there is no BIOS problemor memory conflict.

1. Click on the Windows Start button and then Programs andAdministrative Tools (Common).

2. Click on the Event Viewer icon.3. Choose the Log menu and Application.4. Search for Mode Logger messages.

Note If a bad signature 0xFFFF reported, it is most likely a bad PCLG. Otherinvalid signature are most likely to be a device conflict or a BIOS problem.


Troubleshooting

Problem Procedure

Mode Logger does not run Check the PCLG assemblyCheck cable connection to an active networkCheck for possible memory conflictCheck for possible BIOS problemCheck all Mode Logger configuration settingsCheck for correct net numberCheck for correct location of the Message ArchiverCheck DlanView set upCheck the Windows NT Event Log for errors (event.dbf file), which isaccessed through Programs/Administrative Tools/Event Viewer.

Command message(s) havenet1\drop140\word1\bit0 instead of thesignal name

The signal name cannot be found in the SDB. Check the Windows NTEvent Log to make sure there was no problem initializing from the SDB.Signals may need to be posted or reposted.

Receiving messages from one network butnot the other (with two DLAN+s and twoMode Logger assemblies)

Check that both PCLGs and both Mode Logger programs are running andsending messages to the correct MsgArchiver.Check that the system time on both Mode Logger PCs is the same. ThePCLG time is initially set by the host PC. If one PCs time is slow, all itsmessages appear at the bottom of the list, or not at all if there are a lot ofmessages. To verify that each Mode Logger is sending messagescorrectly, set up a separate MsgArchiver for each Mode Logger. Sendeach Mode Loggers message to its own MsgArchiver. Then, when bothhave been verified separately, send all messages to the sameMsgArchiver.

Device faults appear in DlanView, but notin the CIMPLICITY HMI Alarm Viewer

Check the CIMPLICITY HMI status log on the CIMPLICITY server. (Fromthe CIMPLICITY HMI project, choose the Tools menu, and choose StatusLog). Messages may indicate that alarm IDs are not configured or that aresource is missing. Required alarms must be configured for each deviceusing the CIMPLCITY HMI alarm configuration application. If a resource ismissing, enter it manually, using the Resources icon in the CIMPLICITYHMI project.If there are no errors in the Status Log, there could be a problem in thetransfer of messages from MsgArchiver to the CIMPLICITY HMI AlarmManager. Check all the settings in the Mode Logger ConfigurationProgram. Check that the CIMPLICITY server host name is correct.Check the TCP/IP connection to the CIMPLICITY server. From the DOSprompt type ping . On the CIMPLICITY server, make surethe GECAMS box is checked under Project/Settings, and make sure itruns when the CIMPLICITY project is started. Use the Windows NTEvent Viewer to check the application log for any error indications on boththe Message Archiver PC and the CIMPLICITY server PC.

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 5 DlanView 49

Chapter 5 DlanView

IntroductionThis chapter provides instructions for using the DlanView application to view datacollected by the Mode Logger and Data Logging applications.

ConceptsAlarms are selected messagesthat announce a device orprocess condition

Events are actions, such as acommand message.

DlanView provides two modes to view alarm and event messages. It operatesdifferently, depending on which mode is specified.

Dynamic mode reads and displays the most recent database messages.

Static mode reads the database once and displays those messages read at that time.

If no filter is applied, thedatabase is read periodicallyat the rate specified by theuser in the Setting menu,Update Interval.

DlanView is used to define a filter with specific criteria. The filter can be applied toeither mode, so that only messages that meet the filter criteria are displayed. Earliermessages are removed from the database to provide room for the most recent eventsand alarms. The size of the message database (in either mode) is set in the ModeLogger Control application under Settings and the tab Message Archiver (refer toChapter 4).DlanView provides the following features to display DLAN+ messages:

Online view of messages, which are color coded to quickly identify a particularclass of message

Search command to view a specific subset of messages

Define filter command to specific searches for Dynamic and Static modes

Configurable columns

Integration with Diagnose application for permissive diagnostics

An alarm description dialog box for Help on TXT messages

50 Chapter 5 DlanView GEH-6372D GEMIS Tools for CIMPLICITY

Data FlowThe following diagram displays data flow between Mode Logger and DlanView.

ModeLoggerPC 1

MessageArchiver

Database

MessageArchiver

DLAN+ Messages

DlanView

DLAN+Messages

DLAN+ Network A

SDB

CIMPLICITYAlarm/Event

Database

* Selected message types

PCLG Assembly

Signal Names in DLAN+ Message


W ithin a single PC

Alarm ManagerInterface

CIMPLICITY Alarm API

CIMPLICITYAlarm Mgr

(AMRP)

AlarmView

ModeLoggerPC 2

* Device faults and process alarmstransmitted by DLAN+ devices

CIMPLICITY HMI Project

DLAN+ Network B

PCLG Assembly

Message ColorsDLAN+ messages display in different colors and identify the class of a message asdefined in the table below. Only Mode Logger text (TXT) message colors can beedited (see the section Set Alarm Colors).

Text Color BackgroundColor

Type of DLAN+ Message Alarm_Type

Green Black No Fault messagesWhite Red All Fault messagesWhite Red Mode Logger DLAN+ device fault DVFLT/TRFLTGray Black Mode Logger CCI card message MDLOGWhite Black Mode Logger DLAN+ command message CMDMGWhite Black Mode Logger DLAN+ variable change message VARMGGreen Black Mode Logger DLAN+ device reset of fault condition DVNFTCyan Black Mode Logger permissive diagnostic message PDIAGWhite Black Dynamic group message DYGRPYellow Black Mode Logger text message set TXTSGreen Black Mode Logger text message clear TXTSC

Note The colors of TXTS and TXTSC type messages can be defined by the user.Refer to the section Set Alarm Color.


Using DlanViewDlanView binary (.dvb) files contain the following configuration information: Column configuration

Filter definitions

Display and print font descriptions

Update interval

Current filter settings

Static mode time out value

User defined color settings (TXTx messages only) To start DlanVieww From the GEMIS Tools for CIMPLICITY program group/folder, click the

DlanView icon. The DlanView screen displays.

Note The Message Archiver Message Database location must be defined and thepath must be accessible before any message data will display (see the sectionConfiguration on page 54.

Event/Alarm toggleDynamic/Static toggle

Toggle filter on/offCurrent Display Filter Details

Alarm andEvent messages

Status Barprovidesspecificapplicationinformation,as described

Displays Events & Alarmsor Alarms Only

Displays Filteredor Unfiltered

Displays Static orDynamic Mode

Displays the currentpage number

Name of the CurrentDisplay Filter

Filter searchesare displayed inthis screen

CurrentColumns

Displays buttondescriptions anduser notes

52 Chapter 5 DlanView GEH-6372D GEMIS Tools for CIMPLICITY

View MenuThe View menu has the following commands:

A check mark displays bythe command name when thefeature is enabled anddisplays.

Toolbar toggles to display or hide the shortcut command buttons.Status Bar toggles to display or hide the application information that displays at thebottom of the screen.

Click to toggle eventsand alarms.

Or click to toggle thefilter on and off.

Events & Alarms displays both events and alarms to be shown.Alarms only displays only alarms to be shown.Dynamic toggles between Static and Dynamic display modes. Dynamic will displaywhen DlanView is in Static mode (in order to choose Dynamic). Static will displaywhen DlanView is in Dynamic mode.

Explain provides Help or diagnostics for the selected alarm or event.Toggle Filter on/off activates the Current Display Filter using the existing mode(either Static or Dynamic) of operation.Current Filter Details displays a dialog box that defines the details of the filtercurrently selected.


Setting MenuThe Settings menu has the following commands:

Message database allows you to choose the path of the message database.SDB database allows you to select the server and path to the SDB.Refresh Alarm data from SDB updates the alarm description and alarm classinformation from the SDB.

Column Config specifies which columns display and the order of the columns.Update Interval allows you to specify in seconds how often the display isbrought up to date when in Dynamic mode.

Static Time Out allows you to specify (in minutes) how long to remain in theStatic mode. When the time expires, the mode is switched to Dynamic.

Monospace characters haveexactly the same width,producing characters such asa typewriter.

Define Filters allows you to define filter(s) with specific criteria that is appliedto search the display for messages with the same criteria.

Generate Filter allows you to create a filter based on the criteria of the currentlyselected message on the screen. Then, the filter can be edited

Alarm TXTx Color allows you to set the color for user defined alarms based onthe alarm class (LOW, HIGH, LL).Display Font allows you t