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 purchaser’s 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 1998

Revision C: December 1997

GEMIS Tools for CIMPLICITY®

Configuration 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

Contents

Chapter 1 Overview 1Introduction................................................................................................................................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 Meaning

Bold 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 Publications

GE 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+ Driveris installed )

• Hard disk space (refer to the following section, Product Software for eachproduct 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 Database

System 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 PC’s 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 MonitorDLAN+ 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 ViewNode

ä

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 Manager’s 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 network

1. From File Manager (3.51) or Explorer (4.0) locate the appropriate networkdrive 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 processautomatically 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 product

In 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/RemovePrograms. 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 V03

GEMIS 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 byone 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_Help

Arc

Data

Lock

Log

Master

Screens

Scripts

*.GEF

Project

CIMPLICITY HMI

CIMPLICITY ServerDevice

SDB Server

System Database (SDB)

Resource_A

Resource_B

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


Using SDB UtilitiesÀ To start the SDB Utilities

w 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 Menus

File 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 acomputer’s 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 Command

The 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 Menus

The 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 Project

CIMPLICITY 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 Project’s 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 projectdirectory. 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 PC’s TCP/IP Name (up to 12 characters and optional), and aDescription (optional).

4. Click OK. (These names display in the Work Area).

5. Add a network connection for the CIMPLICITY Server device. From the Editmenu, choose Insert Net.


The Edit NET connection dialog box displays.

6. Enter the Net Name

7. 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_SRTP

If 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+ connection

1. From the Edit NET connection dialog box, in the Net Type text box, chooseDLAN+.

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 registry

1. Enter data for the chosen DLAN+ in the DLAN+ Edit NET connection dialogbox.

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 Server

To 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 Server

1. From the Options menu, choose Select SDB. The Database dialog boxdisplays.

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 location

w From the Work Area, expand the item, SDB Server. The SDB Server and SDBName 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 List

The 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 <-Remove buttons to change the Selected resources touse for the import filter.

Once the selection is made, the Selected Resource List is displayed in the Work Areaas follows:

Note If no Resources are selected for the Resource List, then no signals (points) areimported.


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 tables

w 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:

<DeviceName>_<NetName>.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 Options

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

À To choose import point options

1. From the Options menu, click on Point Data. The Import Device PointOptions 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 Description

HHIGH ALM_HIGH_2 High alarm limit

HIGH ALM_HIGH_1 High warning limit

LOW ALM_LOW_2 Low alarm limit

LLOW 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 points

1. From the Tools menu, choose Import, and choose Points.

2. Choose SDB-Device to import points from a specific device for a givennetwork 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 Utility’s response to import the points.


The following is an example Log window:

.csv FileÀ To import points from a .csv file


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 Alarms

User 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_1

Scale_DefNet_Names

Broadcast Alarms

Alarm_1Alarm_2Alarm_3

Type_Def

Resource

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 Alarms

Each 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 device’s 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 Alarms

Broadcast 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 alarms

1. From the Tools menu, choose Import, and choose Alarms. The AlarmImport 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


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 application

w 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 up

1. From the Mode Logger System Control window (shown above), clickSettings…

The Mode Logger Settings dialog box is displayed. It contains a tab for theMode 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 location0xD0000

J6 Jumper right two pins (LOG)

J5 Install jumper on both pins

J3 Remove jumper, no CPU address

J4 Remove jumper, no CPU interrupt

J7 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 doesn’t, 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 PC’s memory to the PCLG memory. If another device has already mapped thismemory, MapMem fails and Mode Logger does not run.

À To check for conflicts

1. From Windows NT (Version 4.0), Programs, choose AdministrativeTools.

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 messages

Messages 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 assembly

Check cable connection to an active network

Check for possible memory conflict

Check for possible BIOS problem

Check all Mode Logger configuration settings

Check for correct net number

Check for correct location of the Message Archiver

Check DlanView set up

Check 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 Logger’s 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 <hostname>. 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



W ithin a single PC

Alarm ManagerInterface

CIMPLICITY Alarm API

CIMPLICITYAlarm Mgr

(AMRP)

AlarmView

ModeLoggerPC 2



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 messages

White Red All Fault messages

White Red Mode Logger DLAN+ device fault DVFLT/TRFLT

Gray Black Mode Logger CCI card message MDLOG

White Black Mode Logger DLAN+ command message CMDMG

White Black Mode Logger DLAN+ variable change message VARMG

Green Black Mode Logger DLAN+ device reset of fault condition DVNFT

Cyan Black Mode Logger permissive diagnostic message PDIAG

White Black Dynamic group message DYGRP

Yellow Black Mode Logger text message set TXTS

Green 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 DlanView

w From the GEMIS Tools for CIMPLICITY program group/folder, click theDlanView 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


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 to change the font of the message text and columnheading text. Use monospace fonts to view the column fields correctly. The defaultmonospace font is Courier New.

Print Font… allows you to change the current monospace font to a proportionalfont when printing to a printer. Proportional fonts allow more columns to display onone page.

Note If the Alarm TXT Color command is grayed out there are currently no alarmclass entries defined in the SDB or the SDB is not accessible. Alarm Class itemsmust be defined in the toolbox (System Device and posted to the SDB) before thecommand becomes active. Then, choose Refresh Alarm data from SDB to readthe data changed and enable the Alarm TXT Color command.


Configuration

Database LocationsÀ To configure the Message Archiver database location

1. From the Settings menu, choose Message database. The MessageArchiver Database Location dialog box displays.

2. Enter the path of the database or use the Browse button to locate the database.

3. Click OK.

À To configure the SDB database location

1. From the Settings menu, choose SDB Database. The SDB databasedialog box displays.

Refer to the information thatwas entered during theinstallation of the GEMIStools.

2. Enter the Server Name and Path (path location on the SDB Server) to theSDB.

3. Click OK.


Display SettingsThe appearance of the DlanView screen can be configured to display specificcolumns, fonts, and the update interval.

À To configure the display of columns

1. From the Settings menu, choose Column Config. The ColumnConfiguration dialog box displays.

The Current Column list displays the names of the columns currently displayed onscreen.

2. Edit the columns from the Available Column list using the following:

Add->> button allows you to add an Available Column to the list of CurrentColumns. Click on the desired column name in the Available Column list and clickthe Add button, or double-click the desired column.

Remove->> button allows you to remove a column from the list of CurrentColumns. Click on the column and click Remove, or double-click the column.

3. Edit the display order of the columns using the Move Up or Move Downbutton. Click on the column to move and then click Move Up or Move Down.

Use monospace fonts to viewthe column fields correctly.The default font is CourierNew.

À To change the display font

1. From the Settings menu, choose Display Font. The Font dialog boxdisplays.

2. Choose the font to use for the DlanView screen.

À To change the update interval

The default interval rate is 5.The minimum rate(andsmallest number that can beentered) is 1.

1. From the Settings menu, choose Update Interval. The Update Intervaldialog box displays.

2. Enter the Update interval (seconds) and click OK.


OperationThe following section describes other commands used during operation of DlanView.

Obtain Message Help

À To obtain Help on an Alarm or Event message

Or press w From the View menu, choose Explain.

Or, from the DlanView screen, double-click on an Alarm or Event.

The appropriate Help displays based on the type of Alarm/Event message selected.The alarm types for specific Help are as follows:

• PDIAG displays diagnostics.

• TXTx displays an alarm description dialog box.

• Device fault displays a device specific Help file.

• All others display a dialog box with a specific message.

Static Time Out Value

À To specify the Static time out value

Static time out is the amountof time that the screen stays instatic mode before it revertsback to Dynamic.

1. From the Settings menu, choose Static Time out. The Static to Dynamictime out value dialog box displays with the default value 0.

2. Enter the time out value (minutes) from 0 (no time out) to 999.

F4


Define Filters

The command Define Filters... is used to define display filter(s), which controls themessage data displayed on the screen. The Define Display Filter dialog box isdivided into three sections as follows:

Filter Selection allows you to create and delete a filter, edit the filter name, andchoose the current display filter.

Columns Available provides a list of available columns, which are the source ofdata. The list of columns changes, based on the table that is currently selected(Alarms or Events & Alarms).

Display Data Where… contains the filter criteria for the search. The data willchange based on the filter selected in this box.

À To define the display filter

1. From the Settings menu, choose Define Filter. The Define Display Filterdialog box displays.

The field Filter Selection contains the following:

The name entered must beunique in the displayed dropdown list.

If the deleted filter was theCurrent Display Filter thenno display filter is assigned.

• Choose New Filter to create a new filter. The default name is User DefinedFilter x. X is always the actual number of filters in the list, plus one. Edit thisfilter name by clicking on it and typing a new name.

• Choose Delete Filter to delete the selected filter in the Filter Selection text box.

• Click on Current Display Filter to assign the filter displayed in the text box tobe used for the search when applied.


Add Search Values

In the Define Display Filter dialog box, the section Columns Available allows youto define each filter for the search.

À To add search values to a filter

1. From the Define Display Filter dialog box, choose a filter from the FilterSelection drop down text box or click New Filter.

2. From the field Columns Available, click on a display column and click AddWhere. The Match Value dialog box displays.

3. Enter the search value for that column. Or click Browse… (if available).

4. Click OK. The value displays in the Display data where… text box. This valueis applied to the filter search.

5. Repeat the Add Where… selection until all search values are defined.

The section, Display data where… contains the search values for the filter. Theformat is displayed as a logical expression evaluated from left to right (top to bottom)when the filter is applied to the display.

Modify Search Values

À To modify search values

1. From the Define Display Filter dialog box and the section Display datawhere… click on a value and click any of the following buttons.

Modify allows you to change the search value.

Remove deletes the chosen value.

Move Up moves the chosen value up one position in the list.

Move Down moves the chosen value down one position in the list.

And and Or chooses the logical operation to apply.

The number of left and rightparenthesis must match.

Add ( ) and Del ( ) buttons assign parenthesis to group the value and control theevaluation. Parenthesis can be nested.

Not inverts the result of the chosen value.

2. Click on the option box, Match Case to make the search value case-sensitive.The default is to ignore the case when searching.


Generate Filter

In the Settings menu, the command Generate Filter allows you to choose a alarm orevent message from the screen and generate a filter from its values.

À To generate a filter

1. From the DlanView screen, click on a message.

2. From the Settings menu, choose Generate Filter. The Name of Filterdialog box displays.

3. Enter a new unique name and click OK. The Define Display Filter dialog boxdisplays and contains the search value(s) for the selected message.

4. Edit the values of the new filter (see the section Define Filters).

Set Alarm Color

Note If the Alarm TXT Color command is grayed out there are currently no alarmclass entries defined in the SDB or the SDB is not accessible. Alarm Class itemsmust be defined in the toolbox before the command becomes active. Then, chooseRefresh Alarm data from SDB to read the data changed.

À To set TXTx alarm_class color

The text boxes allows you toview the text colors forreadability.

Both the Normal State andAlarm State will change to thedefault colors.

1. From the Settings menu, choose Alarm TXTx Color. The Alarm ClassColor Definition dialog box displays.

2. From the Alarm Class Text list, click on the desired class to set color.

3. From the Normal State or Alarm State, click the Text Color orBackground Color button(s).

4. Choose a color and click OK. The text in the Normal State Color/Alarm StateColor example text boxes change to the chosen color.

5. Click Clear Text Color to change the chosen Alarm Class color to the defaultcolors.

6. Click OK to save the changes and exit the dialog.

Or, click Apply to enable the new colors to the messages on the display screenwithout exiting the dialog box and continue to set colors for other classes in thelist.


These text boxes allowyou to view the chosentext colors for readability.

The button, Clear Text Colorchanges both Normal Stateand Alarm State back to theirdefault colors.NormalState Color = greentext on black backgroundAlarm State Color = yellowtext on black background

User DefinedAlarm ClassText list readsform the SDB

Printing Alarms and Events

À To print alarms and events

w From the File menu choose Print.

If in the Static mode, the entire results of a filter (filtered) or the entire database(unfiltered) is printed.

In the Dynamic mode, only the alarms and events displayed on the screen areprinted.

Note In Static mode, use Page No (lower right corner of the Status bar) todetermine the page number when printing a single page or a range of pages.

ExamplesThe following section provides examples of filter searches. In all of the examples, thefilter shown in the Define Display Filter dialog box is selected as the Current DisplayFilter. The screen that follows shows the results after the filter has been applied.


Single Column SearchThe following is a single column search. The Current Display Filter called AllDiagnostic messages will search the column ALARM_TYPE for all occurrences ofpdiag in the Dynamic mode.

The following screen displays the result of the search for all messages that havepdiag in the ALARM_TYPE column.


Multiple Column SearchThe following filter searches the column ALARM_TYPE for txts And the columnALARM_ID for GN437.

The following screen displays the result of the search for all messages that have txtsin the ALARM_TYPE column And GN437 in the ALARM_ID column.


The following filter searches the column ALARM_TYPE for txts Or the columnALARM_ID for GN437.

The following screen displays the result of the search for all messages that have txtsin the ALARM_TYPE column Or GN437 in the ALARM_ID column.

The following filter searches the column ALARM_TYPE for DVFLT AndALARM_ID for drvf Or oc2f.


The result of the filter search is as follows:


Wildcard SearchesIn addition to And/Or combinations, wild card characters (asterisk and questionmark) can be used in the search string. The asterisk can stand for any character orcharacters that may appear in the same place. *aaaa…, aaaaa*, *aaaaa*. Eachquestion mark stands for any single character.

The following filter searches the column ALARM_TYPE for txts And the columnALARM_MESS for the word ground.



The following filter uses ? as the wildcard placeholder. The filter searches allmessages with GN as the first two characters followed by three additional charactersof any type (GN???).


GEH-6372C GEMIS Tools for CIMPLICITY Chapter 6 Network Time Protocol (NTP) • 67

Chapter 6 Network Time Protocol (NTP)

IntroductionIn a customer requisition, thesetup utility can be configuredat GE with the GE Mastertime sever. Then, if the basicconfiguration rules arefollowed, no configuration isrequired to set up the systemat the job/customer site.

This chapter provides an overview of the Network Time Protocol (NTP) and adescription of the individual Services. NTP is a service used to synchronize the timeof a PC (Client) to another PC, which is the time source (Master). It provides Clientsynchronization within 10 milliseconds (ms) of the Master on local networks. NTP isconfigured during installation through the setup utility.

NTP Diagnostics provides a window interface to the ntpq utility to monitor the statusof the NTP Service (refer to the section NTP Diagnostics). NTP Status Indicatordisplays a clock icon to show the synchronization status of the service (refer to thesection NTP Status Indicator).

ConceptsThe NTP installation is configured to use the GE Master time server at GE. NTPdoes not require reconfiguration when it is shipped to the customer site, if thefollowing basic configuration rules are followed:

Refer to the next section,Operating Modes.

• Use the same NTP operating mode (either Broadcast or Unicast) for every nodein a requisition.

• Set up only one Master per requisition.

GE Master Time ServerThe GE Master time server, MMI-WKS is synchronized to provide a reliable timesource for hosts running NTP. MMI-WKS broadcasts NTP packets every 64 secondson the 165.156.xxx.xxx subnet (Broadcast mode). MMI-WKS can also be polleddirectly (Unicast mode) at address 165.156.8.173.

The NTP installation configures the Master node to synchronize to its internal clock,if a remote time source is not available. Therefore, an NTP configuration that wassynchronized to MMI-WKS does not need to be modified when the requisition ships.

Also, the Unicast Master node allows a Secondary time source, which specifies the IPaddress of the existing Master node at the customer site. Again, reconfiguration of theMaster node is not necessary.

68 • Chapter 6 Network Time Protocol (NTP) GEH-6372C GEMIS Tools for CIMPLICITY

Sending a directed messageis required because broadcastmessages are not repeated toother subnets across Ethernet.Unicast messages are directedand are therefore not limitedto a particular subnet.

The ntp.ini file can be foundin C:\Winnt.

The installation configures the Broadcast Master nodes to receive and broadcastpackets, so that they will automatically receive broadcasts from the GE time server orany Broadcast Masters at the customer site.

Note To synchronize to MMI-WKS using Broadcast mode when a requisition isconfigured on a subnet other than 165.156.xxx.xxx, it may be necessary to manuallyadd a Unicast polling (directed message) of MMI-WKS to the ntp.ini file of theMaster node. To manually add a Unicast polling of MMI-WKS to a BroadcastMaster, add the following line of code to the ntp.ini file of the master: server mmi-wks.

Operation ModesThe GEMIS Tools for CIMPLICITY installation supports the following NTP modes:

Broadcast mode periodically broadcasts packets from a Master node. A Master nodeis established for each requisition that broadcasts to the subnet address correspondingto the Master’s IP address. For example, if the current Master host address is165.156.2.1, the Master broadcasts to 165.156.255.255.

For more information on thestratum level, see the section,Monitoring on page 81.

Client nodes receive broadcasts from all Master nodes broadcasting on the samesubnet. Client nodes generally synchronize to the lowest stratum Master.

Unicast mode sends a directed message (poll) from each Client node to the specifiedMaster node. The Master node sends a reply (another directed message) to the Clientnode that sent the original message.

Unicast mode is more accurate than Broadcast mode because the network delays canbe precisely measured in each direction (as opposed to the Broadcast mode where thenetwork delay can only be approximated from the total delay time). As the number oftime samples increases and the refinements to the local clock become smaller, theUnicast Client nodes increase the time between requests for new time data from theMaster node.

Note Multicast mode is no longer supported by the GEMIS Tools forCIMPLICITY installation.

Using NTPNTP must be installed oneach PC that needs timesynchronization. Designateone PC as the time Master.

NTP is installed during setup with other GEMIS Tools for CIMPLICITY products(see Chapter 2). Choose the NTP product from the dialog box, GEMIS Tools ForCIMPLICITY product selection.

Follow the instructions provided by setup. The setup utility configures the NTPservice based on the user’s replies to the setup questions. The product is installedcomplete and operational.


If NTP is already installed, the following dialog box displays. Choose to remove theNTP Service or update to this version.

If the ntp.ini (NTP configuration file) was manually edited, the following dialog boxdisplays:

Note To include these modifications in the new ntp.ini file created by setup, savethe original copy of the ntp.ini file before continuing and manually edit the file afterthe installation is complete.


Configuration

Broadcast Time Master Node SetupUpon installing NTP from the product selection dialog box, the user must reply tosetup options as follows:

À To configure the PC as a Broadcast Time Master

1. Choose Configure as a Time Master from the following dialog box.

2. Choose the Broadcast mode of operation.

3. Click Next. The ntp.ini is configured, the local time is automatically set to thesame value as MMI-SKS if it can be located on the network, and the NTP service isstarted.


Unicast Master Node SetupÀ To configure the PC as a Unicast Master

1. Choose Configure as a Time Master from the following dialog box.

2. Choose the Unicast mode of operation.


3. Choose whether to synchronize to the local clock or to a remote time source.

If Choose Time Master(s) is chosen, the following dialog box displays.

Primary Time Master always defaults to the GE Master time server, MMI-WKS.

Secondary Time Master specifies a time source that exists at the customer site.

4. If a plant wide Time Master source exists at the customer site, enter the name ofthe site Time Master.

5. Click Next. The ntp.ini is configured, the local time is automatically set to thesame value as MMI-WKS (if it can be located on the network), and the NTPservice is started.


Broadcast Client Node SetupÀ To configure the PC as a Client

1. Choose Configure as a Client from the following dialog box.

2. Choose the Broadcast operation mode.

3. Click Next. The ntp.ini is configured, the local time is automatically set to thesame value as MMI-WKS if it can be located on the network, and the NTPservice is started.


Unicast Client Node SetupÀ To configure the PC as a Unicast Client

1. Choose Configure as a Client from the following dialog box.

2. Choose the Unicast operation mode.


3. Enter the Host Name or IP address of the PC chosen as the Time Master.

4. Click Next. The ntp.ini is configured, the local time is automatically set to thesame value as MMI-WKS (if it can be located on the network), and NTP isstarted.

ProgramsThe following programs are automatically installed in the NTP subdirectory. Formore information refer to .html product documentation, also installed in C:\GEMIS-MMI\NTP\htmldoc.

ntpdate operates like theUNIX program rdate, but ismuch more accurate.

xntpd manages the time on the Master and Client PCs.

ntpq queries local and remote NTP PCs for state variables and related time keepinginformation. This program conforms to Appendix A of the NTP Version 3Specification RFC 1305.

xntpdc queries local and remote NTP PCs for state variables and related timekeeping information. This program is specific to Version 3 of NTP and does notconform to Appendix A of the NTP Version 3 Specification RFC 1305.

ntpdate sets the local PC time from one or more remote PCs running NTP.

ntptrace can be used to reveal the chain of NTP PCs from a designated PC to theprimary server at the root of the time keeping subnet.

ntp.ini Filentp.ini file can be edited withany text editor, such asWindows NT Notepad.

The ntp.ini file is a text file that provides the startup parameters for the xntpd service.This file is created by the setup program during installation. Changes to the ntp.inifile do not become effective until the NTP service is stopped and restarted.

This document isautomatically installed in theNTP directory.

Note Normally it is not necessary to edit the ntp.ini file. However, if the Service isnot operating properly, consult the full product documentation in the directoryGEMIS-MMI \Ntp\htmldoc. Refer to the readme.txt file to view the HTML Helpfiles.


The following is an example of an ntp.ini file for a Broadcast Master node :## Provides the NTP Service its startup parameters and# list of startup files.## Refer to the HTML documentation (in the C:\GEMIS-MMI\NTP\htmldoc directory)# for complete details on the options supported.# See readme.txt in the htmldoc directory for setting up the html files.### -------- Time Master Server entries ------# For server shemp @ addr 165.156.8.166#server 127.127.1.0 prefer # Use this PC as time master serverfudge 127.127.1.0 stratum 12 # Use local clock on server as time sourcebroadcast 165.156.255.255 minpoll 6broadcastclient##driftfile C:\GEMIS-MMI\NTP\ntp.drift # path for drift file## --- Remove comment to activate debug files in stats dir ----# statsdir C:\GEMIS-MMI\NTP\stats\ # directory for statistics files# statistics loopstats peerstats

The following is an example of an ntp.ini file for a Unicast Master nodesynchronized to the server MMI-WKS with Shemp as a secondary time source:

## Provides the NTP Service its startup parameters and# list of startup files.## Refer to the HTML documentation (in the C:\GEMIS-MMI\NTP\htmldoc directory)# for complete details on the options supported.# See readme.txt in the htmldoc directory for setting up the html files.### -------- Time Master Server entries ------# For server shemp @ addr 165.156.8.166#server 127.127.1.0 prefer # Use this PC as time master serverfudge 127.127.1.0 stratum 12 # Use local clock on server as time source## Comment out the following line to remove MMI-WKS as time source.server MMI-WKSserver Shemp##driftfile C:\GEMIS-MMI\NTP\ntp.drift # path for drift file## --- Remove comment to activate debug files in stats dir ----# statsdir C:\GEMIS-MMI\NTP\stats\ # directory for statistics files# statistics loopstats peerstats


The following is an example of an ntp.ini file for a Broadcast Client node:## Provides the NTP Service its startup parameters and# list of startup files.## Refer to the HTML documentation (in the C:\GEMIS-MMI\NTP\htmldoc directory)# for complete details on the options supported.# See readme.txt in the htmldoc directory for setting up the html files.### -------- Client entry --------------------#broadcastclient##driftfile C:\GEMIS-MMI\NTP\ntp.drift # path for drift file## --- Remove comment to activate debug files in stats dir ----# statsdir C:\GEMIS-MMI\NTP\stats\ # directory for statistics files# statistics loopstats peerstats

The following is an example of an ntp.ini file for a Unicast Client node:## Provides the NTP Service its startup parameters and# list of startup files.## Refer to the HTML documentation (in the C:\GEMIS-MMI\NTP\htmldoc directory)# for complete details on the options supported.# See readme.txt in the htmldoc directory for setting up the html files.### -------- Client entry --------------------#server newt##driftfile C:\GEMIS-MMI\NTP\ntp.drift # path for drift file## --- Remove comment to activate debug files in stats dir ----# statsdir C:\GEMIS-MMI\NTP\stats\ # directory for statistics files# statistics loopstats peerstats

Startup OptionRefer to the section ServiceProgram.

The NTP consists of a Service (xntpd.exe) and supporting programs used fordebugging and support.

Refer to the section, ntp.iniFile.

When setup is complete, the file ntp.ini is created in the Windows system directory.This text file contains the configuration settings for proper operation.

Service ProgramThe Service program manages all NT services including NTP. The startup for eachservice can be selected as automatic, manual, or disabled. The default for NTPstartup is set at automatic.

À To activate the Service dialog box

In Windows 3.51, from theProgram Manager, double-click the Control Panel icon.

1. Click Windows Start button, Settings, and Control Panel.

2. Double-click Services icon.


The following dialog box displays.

3. Click on the service to edit, such as Network TimeProtocol (shown above).

4. Click on Stop to shut down the service and Start to start it up again.

À To change the Startup Type for the service

Click .

1. From the Services dialog box (shown above), click on the service to edit.

2. Click on Startup…. The following dialog box displays.

Automatic starts the NTPwhen the PC is started.

Manual allows the user to goto the Control Panel to turnon NTP.

Disabled turns the NTP off,never to run until the StartupType is changed.

3. Click either Automatic, Manual, or Disabled.

4. Click OK. The new Startup Type displays in the Services dialog box.


OperationDuring operation, xntpd Service writes the operation events to the Event Viewer.

À To check for proper operation

Double-click on 1. From Programs, choose the Administrative Tools program group/folder.

2. Click the Event Viewer icon. The Event Vewier - Application displays.

3. From the Log menu, choose Application. The Application Log events aredisplayed.

4. From the column Source, click the latest NTP entry to highlight it.

5. Then, double-click on the entry. The following Event Detail dialog boxdisplays with a text message that describes that event.

Source Column

Log Menu


Multiple entries can occurbefore synchronization, thenthe service starts again.

After a period of time, synchronization to the time Master occurs. The text messagein Event Detail indicates that this PC is synchronized to the time Master.

If there is a time difference of more than a minute between the Client and the Masternode, there can be a delay before time synchronization is achieved. This delay can beminimized by stopping the NTP from the Service program and setting the Client timeto the current value of the Master node (see procedure below).

Also, if the time difference between the Master and the Client nodes is greater than2000 seconds, the NTP automatically shuts down before synchronization is achieved.The NTP sends the message, time error is way too large (set clock manually) to theEvent Viewer. Again, if the NTP service shuts down due to a large time error, set theClient time to the current value of the Master node (see procedure below).

À To set the local time to the same value as the Master node

w From the MS-DOS command prompt on the client PC, type the commandntpdate <master> (<master> is the current Master PC).


MonitoringAfter NTP is started, it seldom writes to the Event Viewer. Use the ntpq program tomonitor the NTP during normal operation. Each time ntpq runs, it produces a table ofdata indicating the current status of NTP on the PC specified.

À To monitor the NTP program

1. From the MS-DOS command prompt, change directory to gemis-mmi\ntp.

2. Type ntpq -p <hostname>

where

-p is the option to list the NTP Master(s) recognized by the <hostname>

<hostname> is any PC hostname that has NTP installed and enabled

This is a sample output after the command ntpq -p <hostname>:

remote refid st t when poll reach delay offset disp

*<master>.salem.ge LOCAL(0) 7 - 21 64 3 0.00 4.996 17.41

The data fields are as follows:

remote is the name of the master node. The asterisk character (*) indicates that thisnode is the current Master node, which shows that synchronization with this node hasoccurred. The * also indicates the currently selected Master node if there were morethan one potential master node in the system configuration. The character # beside ahost name indicates that the host is a potential time source.

refid shows the current source of synchronization for the Master node.

st shows the stratum level of the Master node. The stratum level is a declaration ofthe quality of the time source. Lower stratum numbers indicate a more accurate timesource.

when is the time in seconds since the last broadcast from the Master (Broadcastmode) or since the Master was polled by the client (Unicast mode).

poll is the broadcast frequency of the Master node (defined in the ntp.ini file by theminpoll parameter (2^minpoll)).

reach is an indication of the responsiveness (reachability) of the time source.

delay is the communication delay between the Master and Client nodes inmilliseconds.

offset is the time difference between the Master and Client nodes in milliseconds.

disp (dispersion) is a measure of how well the local time is tracking the Master timesource. Smaller numbers indicate better tracking accuracy.


This is another sample output after the command ntpq -p <hostname>

where

<hostname> is the Master using its internal clock as the time source

remote refid st t when poll reach delay offset disp

*LOCAL(0) LOCAL(0) 6 - 47 64 377 0.00 0.00 17.81

<MASTER> 0.0.0.0 16 u - 64 0 0.00 0.000 16000.0

If the NTP service is not running on the <hostname> PC (where <hostname> is theMaster or Client) and the ntpq command is issued, the following error message iswritten to the MS-DOS command prompt screen:

<hostname>.salem.ge.com: timed out, nothing received

***Request timed out

NTP DiagnosticsNTP Diagnostics can monitor the status of the NTP Service on any specifiedcomputer on the network. The application periodically polls the service and displaysdata about the NTP. NTP Diagnostics provides a windows interface to the ntpq utilityand is installed with the NTP product installation (as part of GEMIS Tools forCIMPLICITY).

StartupTo start NTP Diagnostics

w From the GEMIS Tools for CIMPLICITY program group, choose NTPDiagnostic.

Or, in Windows NT 4.0 and later:

Choose NTP Status Indicator and with the right mouse button, click on the

icon (located on the right side of the taskbar). From the pop-up menu, clickCreate a new NTP Diagnostics window.

Or, double-click on the icon with the left mouse button.

Or, from the MSDOS prompt, change to the directory where NTP is installed(usually C:\GEMIS-MMI\NTP) and enter the command ntpdiag.

The NTP Diagnostics application starts and the NTP Diagnostics window displays(refer to the next page).

À To exit NTP Diagnostics

w For the NTP Diagnostics window, choose the File menu and Exit.

Or, click on in the top right of the window.


Note The NTP Diagnostics window size and font are automatically selected basedon the active video mode and cannot be changed by the user.

ConfigurationThe NTP host name is the only configurable item for this application. The defaulthost name is localhost, which displays data for the NTP service running on the localcomputer.

À To display data on a remote computer

1. From Configure menu, choose Set Host. The following dialog box displays:

2. Enter the name or IP address of the remote computer.


OperationWhen the NTP Diagnostics starts up or when a new host is selected by the user, theapplication indicates that it is waiting for a reply from the specified host as follows:

The application displays data and periodically (about every 5 to 10 seconds) updatesthe data as it is received from the specified host as follows:

• Data that corresponds to the node that the computer is synchronized to isdisplayed against a green background.

• Data that corresponds to any potential time source displays against a yellowbackground.

• All other data displays against a white background.

The data fields are defined as follows:

remote is the name or IP address of each remote time source. The asterisk character(*) indicates the current Master node, which shows that synchronization with thisnode has occurred. The plus character (+) indicates that the host is a potential timesource.

refid shows the current source of synchronization for the remote time source.


st shows the stratum level of the remote time source. The stratum level is adeclaration of the quality of the time source. Lower stratum numbers indicate a moreaccurate time source.

t shows the data gathering method used, such as u = unicast, b = broadcast.

when is the time in seconds since the last broadcast from the time source (Broadcastmode) or since the time source was polled by the client (Unicast mode).

poll is the broadcast frequency of the time source or the polling rate of the clientnode (defined in the ntp.ini file by the minpoll parameter (2^minpoll)).

reach is an indication of the responsiveness of the time source.

delay is the communication delay between the time source and the local node inmilliseconds.

offset is the time difference between the time source and the local node inmilliseconds.

disp (dispersion) is a measure of how well the local time is tracking the remote timesource. Smaller numbers indicate better tracking accuracy.

NTP Status Indicator

The icon displays in thelower right of the Windowstaskbar

The NTP Status Indicator displays the synchronization status of the NTP servicethrough a clock icon. The icon has associated tool tips, which enumerates thesynchronization status of the machine, including the name or IP address of the nodethat the local machine is synchronized to. NTP Status Indicator is installed with theNTP product installation (as part of GEMIS Tools for CIMPLICITY). It alsoprovides convenient access to NTP Diagnostics.

Note The NTP Status Indicator is not compatible with versions of Windows NTprior to 4.0 (since these earlier versions did not implement the taskbar functionality).

OperationÀ To start the NTP Status Indicator

w From the GEMIS Tools for CIMPLICITY program group, choose NTPStatus Indicator

Or, from the MSDOS prompt, change to the directory where NTP is installed(usually C:\GEMIS-MMI\NTP) and enter the command ntpdiag -s.

The NTP Status Indicator starts. An icon displays in the lower right of theWindows taskbar. Refer to the next section, Operation for icon status definitions.

The NTP Status Indicator queries the NTP service running on the local computerapproximately every 15 seconds and updates the clock icon in the Windows taskbar.The icon graphically displays the NTP synchronization status of the computer.

Tip ¬ Hold the cursor over the clock icon to generate a tool tip that enumerates thesynchronization status of the machine and the name or IP address of the node that thelocal machine is synchronized to.


Menu Commands

The NTP Status Indicator menu commands can:

• close the application

• start the application automatically whenever the computer is logged on

• create NTP Diagnostic window(s) to display NTP data

• access online Help

À To operate the menu command

w Click on the icon with the right mouse button. The following pop-up menudisplays:

Click this command toclose the window. Theicon disappears and theapplication must bereopened.

This command togglesthe auto start. Acheckmark indicatesthat the command is on.

Click here for onlineHelp. Click here to create a

new window and viewspecific NTP data.

Icon Status

When the NTP Status Indicator starts, the clock icon displays in the Windows taskbar(right side). The icon status reflects the synchronization as follows:

Icon Status Color ofclock face

Not running white withred X

Waiting for feedback from the NTP service(displays when application starts)

white

NTP service is not synchronized red

NTP service is not synchronized, but haslocated at least one potential time source

yellow

NTP service is synchronized green

The icon design looks like aclock only to convey that it isrelated to the system time. It isnot intended to reflect theactual system time.

The NTP Status Indicator icon is animated to indicate that the application is activelyreceiving data from the NTP service. Every time the NTP service returns data to theapplication, the minute hand of the clock icon moves one position. The hour hand ofthe clock icon always remains at the horizontal (3 o’clock) position.

Tip ¬ Only one instance of the NTP Status Indicator can run on the computer (toavoid wasting system resources displaying redundant information). Do not attempt tostart the application when another instance of the application is already running.

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 7 Alarm Manager Service • 87

Chapter 7 Alarm Manager Service

IntroductionThe GE CIMPLICITY Alarm Manager Service (GECAMS) receives messages fromthe Message Archiver and sends them to the CIMPLICITY HMI Alarm Managerthrough the Application Program Interface (API). GECAMS is integrated andcontrolled with the CIMPLICITY HMI project.

ConceptsThe CIMPLICITY HMIProduct must be installedbefore this application can beinstalled.

GECAMS is installed during setup with other GEMIS Tools for CIMPLICITYproducts (see Chapter 2). Choose the product from the following dialog box,GEMIS Tools For CIMPLICITY product selection .

Note After the GECAMS product is installed, it must be selected in theCIMPLICITY HMI Program Properties dialog box. This selection makes GECAMSautomatic whenever a CIMPLICITY HMI project is configured.

88 • Chapter 7 Alarm Manager Service GEH-6372D GEMIS Tools for CIMPLICITY

The following diagram is a simplified data flow for GECAMS.

UC2000V

CPUPS

Ethernet

Alrm_Rt.VSD

CIMPLICITYHMI

Server

DLAN+

Alarm_XMITAlarm_XMIT

TXTV Msg’s

ModeLogger

TXTXV Messages

AlarmManagerInterface

AlarmManager

CIMPLICITYHMI

Viewer

AlarmView

Alm Vw

Alarm

Alarms Status

All Messages

AlarmDatabase

AC/DC2000 Drive

Fault

MessageArchiverDatabas

PCLG Assembly

MessageArchiver

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 7 Alarm Manager Service • 89

Using GECAMSAlarm Manager Service runsautomatically with aCIMPLICITY project.

À To enable GECAMS for a specific project

1. From the CIMPLICITY HMI group/folder , choose Project and thenSettings. The Project Properties dialog box displays.

2. From the tab General, under the Options: text box, click on GECAMS.

GECAMS receives messages from the Message Archiver through TCP/IP overEthernet. It calls API routines to pass alarms to the CIMPLICITY HMI AlarmManager.

Also, refer to Chapter 3 ofthis manual, SDB Utility,Importing Alarms.

In order for the CIMPLICITY HMI Alarm Manager to understand these messages, acertain set of alarms must be defined in the CIMPLICITY HMI Alarm system. Thesealarms are defined in the System Device (see GEH-6333, GE Control SystemToolbox, Chapter 10).

Note GECAMS program is started and stopped in the CIMPLICITY HMI ProjectProperties dialog box.

90 • Chapter 7 Alarm Manager Service GEH-6372D GEMIS Tools for CIMPLICITY

Note

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 8 Diagnose • 91

Chapter 8 Diagnose

IntroductionThis chapter describes the Diagnose application, which translates permissive faultdiagnostic messages from DlanView and CimView applications. In the system, aUC2000 broadcasts a fault diagnostic message on the DLAN+. The Mode Loggerreceives the message and stores it in the Message Archiver Database, including thetime it was received. This message can be translated by DlanView. Live messages aretranslated by CimView.

ConceptsDiagnostic messages are processed by DlanView (message) or CimView (live).

DlanView

Before the Diagnoseapplication can be used, itmust be configured with thelocation of the MessageArchiver Database. Refer tothe tab, System/MessageArchiver Database in theSettings menu.

• In DlanView, selected parts of the diagnostic message are displayed in the colorcyan. The user double-clicks on this message to initiate the Diagnosticapplication to identify the diagnostic message.

• The Diagnose application retrieves the message from the Message ArchiverDatabase and sends in back to the originating UC2000.

• The UC2000 translates the diagnostic message and sends a response back to theDiagnose application. It displays in the Diagnostic window as a relay ladderdiagram (RLD).

CimView

• In CimView, the user requests more information by selecting an object(engineering configured). This is known as a what if request.

• The Diagnose application uses live data to locate the signal in the SDB andretrieve additional information about the UC2000 device.

• The Diagnose application sends the request to the UC2000. The UC2000responds with a snapshot of the current state of the diagnosed signal andoptionally a back-chained set of contacts.

• The diagnostic application then displays the results on screen. The contactsdrawn represent only those signals that are in a loss of power state at that instantin time. It is not the total control logic.

92 • Chapter 8 Diagnose GEH-6372D GEMIS Tools for CIMPLICITY

The following figure shows the data flow in the system using both DlanView and CimView.

SDB

Ethernet

CimView

321

Low Pressure Hydraulic Power System

DLAN+

Raw Diagnostic

Message

UC2000V

CPU

ModeLogger

PCLG Assembly

PermissiveDiagnostics

CimView

Boolean Signal

Signal for Message


Within a single PC

Signal Details

DlanView

Diagnostic message selected

DlanView

Status signal

BENG

Status

PENG

Status

Diagnostic request

All Messages

MessageArchiverDatabase

MessageArchiver

All Messages


Using DiagnoseThe Diagnose application can display data in four modes. The current mode willdisplay in the Status bar. The modes are as follows:

FAULTED displays when the user chooses (double-click) a diagnostic messagedisplayed in DlanView fault diagnostics from the UC2000 displays as an RLD.

LIVE data allows the user to back-track any signal. LIVE data is displayed as TRUE,FALSE, or DON’T CARE.

FILE displays when a .dia file is opened.

NEW displays when a file is crested form the File menu command, New.

Status Bar Display Source of Diagnostic

FAULTED DlanView (blue diagnostic message)

LIVEClick Live Diagnostic Request or CimView

FILE Disk file

NEW DOCClick or from File menu, choose New

RLD Logic and Signal Detailsview settings can be edited inthe Options menu.

The Diagnose window has two views to display the fault diagnostic (see thefollowing screen). The left view is the RLD Logic for the chosen fault diagnostic.The right view display the Signal Details for the contact or coil currently highlightedin the RLD Logic view.

The window title/block name is the name of the block. It is displayed with a periodcharacter (.) in place of the backslash (\). For example, func1\out2 is the name of theblock and FUNC1.OUT2 will be the name in the window title. The period allows thediagram to be saved to a file using the name of the block as the filename.


Below the window title\block name are menus and a toolbar, which can be used toperform different commands. These are described in the following sections.

From the RLD Logic view (left side), click on a contact or coil. Its signal data isdisplayed in the Signal Details view (right side). Double-click on the contact or coilto display additional data. The Signal Details data can include the signal name, itsstate, description, fault type, time the diagnostic data was displayed, and other data.

SignalDetails

Fault DiagnosticActive View ModeStatus Bar

Menu Bar

Toolbar

RLD Logic (diagnosticdata form UC2000)Double-click on the contactto get additional data.Click on the coil for theblock type, fault type, andthe time of data display.

Window Title/Block Name


Menus Commands

File Menu

The File menu, shown below, allows the user to perform file operations with thecommands listed.

New creates a new diagnostic window to use when requesting live diagnostics.

Open displays a previously saved Diagnose file (.dia).

Close exits the present Diagnose window.

Save allows the currently displayed diagnostic to be saved to a file.

Save As allows the current diagnostic to be saved to a file specified by the user.

Print… provides a paper (hard) copy of the current diagnostic file. It uses theoptions that were checked by the user in the Options menu under Settings and the tab,Print.

Print Preview displays the current diagnostic page as it would be printed on paper.

Print Setup… allows the user to choose a printer and printer connection.

File 1,2,3,4 lists and opens the last four previously opened files.

Exit closes the diagnose application.

View Menu

The View menu shown below, allows the user to display or not display the Toolbarand Status Bar in the Diagnose window.

Toolbar displays or hides the toolbar selections at the top of the Diagnose window.

Status Bar displays or hides the Status Bar.


Options Menu

The Options menu shown below, allows the user to manage the options required forproper operation. It also contains setting to manage the appearance of the diagnosticsdata on screen.

Settings allows the user to set options that determine the amount and appearance ofdata that displays in the Diagnose window, such as the display size and fonts.

Rediagnose can be used to recover from a communication error. It reprocesses anddisplays the last diagnostic that displayed on screen. This diagnostic replaces thecurrently displayed diagnostic.

Or click or double-clickon the contact or coil.

Signal Details displays the details window for the currently selected contact or coil.To define which details to display, refer to the tab, Signal Details in the Settingsmenu (see page 101).

Or click Signal Memo displays the note information from the SDB for the currently selectedsignal contact or coil in the RLD view.

Or click Live Diagnostics allows the user to enter data to request a live diagnostic. Thisdisplays the current state of the signal (coil) and why the signal is in this state.

Or click Change Detect is active when a diagnostic is received from a PENG-D block. Thedefault is to display all signals that have changed state that resulted in a loss of powersince the last scan of the UC2000. Choosing this menu item results in a completediagnostic independent of changes per scan.

Window and Help Menus

The Window and Help menus have the same commands as standard Windows-basedsoftware. The Windows menu determines how a window is displayed on the screen.The Help menu contains the current revision number and starts the online Helpapplication.


Toolbar CommandsThe Diagnose application has the following shortcut toolbar commands, which canbe used instead of the menu bar.

Click… To

Create a new file.

Open an existing file.

Save a file.

Print a paper (hard) copy of the active document using the currentprinter settings.

Display additional signal data for the currently highlighted contact or coil.The button appears pressed, if signal details are available.

Display user entered notes from the SDB for the currently highlightedsignal in the RLD view.

Toggle Signal/Label displays (either the signal name or an internallygenerated label) above the contact. A larger percentage of the diagramcan be viewed when the label is displayed.

Increase the size of the contents in the selected view (either RLD orSignal Details view). The text point size is increased by two points.

Decrease the size of the contents in the selected view (either RLD orSignal Details view). The text point size is decreased by two points.

Turn the RLD grid on and off.

Request a live diagnostic. Live Diagnostic Request displays the currentstate of the signal (coil) and why the signal is in this state.

Perform a complete diagnostic separate from changes per scan. ChangeDetect is active when a diagnostic is received from a PENG-D block.The default displays all signals that have changed state and resulted in aloss of power since the last scan of the UC2000.

Obtain context sensitive Help on the selected item. Click on the ? buttonand then click on the desired item.


SettingsThe Options menu contains five tabs that define display and window settings:

Note The tab, SDB/Message Archiver Database must be entered before the Diagnoseapplication can be used with DlanView.

SDB/Message Archiver Database sets the location of the SDB and MessageArchiver Database.

Relay Ladder Diagram Options defines the settings for the RLD Logic Display,such as the text display and grid.

Signal Details selects the items to be displayed in the Signal Details window, such asthe network name, I/O device type, and device location.

Print Options sets the items that are printed and the desired fonts.

Screen Display Options sets the size and position of the screen window, whichinclude the RLD Logic Display (left side) and Signal Details (right)


Relay Ladder Diagram OptionsThis tab defines how the RLD Logic Display is displayed on the screen.

Relay Ladder Diagram Text Display defines how the contacts are displayed.

Use Signal Name is thedefault setting.

Use Label displays an internally generated label over each contact in the RLD.Use this option to allow more contacts to be displayed on the screen for largediagrams.

Use Signal Name displays the logical signal name over the contact.

Display Grid displays a grid pattern on the screen that separates each contact forviewing.

Set Display Text Font defines the font for the text that displays above the contact.

Display Default Signal Prefix enables the prefix portion ( }00000\}00001\B20 ) forsignals that are automatically generated by the UC2000.


SDB/Message Archiver DatabaseThis tab allows the user to set the path for the database(s).

SDB sets the Server Name and Path to the System Database. If the SDB is on thesame PC as the Diagnose application, localhost can be used as the server name. Thepath is relative to the server name.

Message Archiver Database isdefaulted, if the MessageArchiver is installed on thisPC.

Message Archiver Database sets the path to the Message Archiver Database.


Signal DetailsThis tab defines the particular information for each signal that is displayed in the SignalDetail window.

To choose a detail, click onthe box. A check displays inthe box .

To remove a detail, click onthe check box again.

Signal Details allows the user to define which items will display for the desired signal.

IO Device Details allows the user to define which I/O device items will display for thedesired signal.

Descriptions allows the user to define which group of descriptions will display for thedesired signal.

Signal Description Language sets the language for descriptions to be displayed in.

Clear All Selections cancels all items set in this tab. The Language code is notchanged.

Set All Selections sets all items in this tab. The Language code is not changed.

Set Signal Display Font defines the font to display the signal details on the screen.

Note The font that is chosen also applies to the printing of the signal information.


Print OptionsThis tab defines what is printed and the font settings for both the RLD display and SignalDetails.

To preview how the diagramwill be printed, choose theFile menu and Print Previewcommand.

RLD Options prints the RLD to the default printer.

Set RLD Text Font defines the font for the text above the contact.

Signal Details Options prints all of the signal information that is chosen in the SignalDetails tab.

Set Signal Text Font defines the font for the text of the signal details.

Note The tab, Signal Details defines particular information of the signals.


Screen Display Options

This tab defines how the application window is positioned on the screen. It alsoallows the Diagnostic window to be maximized on startup.

Maximize Document Window on Startup enlarges the Diagnose window to thefull size of the screen within the application.

Application Window on Startup has the following options:

Default indicates that the application position and size at startup will be thedefault.

Maximize enlarges the diagnose window to the full size of the screen.

Specify allows the user to customize the location of the application on screenalong with the applications width and height. The maximum height and widthallowed is controlled by the screen resolution setting.


Configuration

StartupCimView requests do not usethe this database.

Before the Diagnose application can be used, it must be configured with the locationof the Message Archiver Database. The database path must be assigned before thefirst diagnostic request is sent to the application from DlanView. See the section,Settings, System/Message Archiver Database on page 100 for more information.

Command Line ArgumentsThe command line argumentsmust be used in the CimViewcommand procedure.

The diagnose application accepts the command line:

DIAGNOSE /SIG signal name [ device name]

where:

/SIG is required

signal name is a valid point ID that equates to a Boolean signal from a UC2000device. Signal name is required. The format of the signal must use the internalUC2000 form module\signal and the signal must be posted to the SDB.

device name is the device that owns the signal (usually a UC2000) that has beenentered in the SDB.

Note The bracket characters [ ] are not part of the device name. They imply thatthe information contained inside the brackets is optional.

À To enable the Diagnose application from CimView

1. From the CimEdit application, choose the object that contains the diagnosticsfault animation object.

2. From the Edit menu, choose Properties, and choose the tab, Procedure.

3. Click New to create a new on mouse down or on mouse up event.

4. From the Procedure Information dialog box, choose Action type andExecute.

5. Enter the executable filename and the command line arguments.


Live DiagnosticLive fault diagnostics can be requested for a signal. The request will return thecurrent state of the signal (coil) and why the signal is in this state.

À To request live diagnostic data

1. From the Options menu, choose Live Diagnostics… The Live Diagnosticdialog box displays.

2. Enter the required information as follows:

Signal Name is the signal to be back-chained. This should be a Boolean signal inthe UC2000 (output of a BENG-D or PENG-D block). Enter a name in the standardUC2000 format (module\signal) or choose from the drop-down list, which containsall the valid signal names used so far.

Browse allows the user to find a signal on the current SDB.

Device Name is the name of the UC2000 device that owns the signal.

Continuous back-chains the signal regularly every few seconds. If this option is notchecked, the signal is back-chained only once.

The signal is back-chained and its state displays as follows:

If the signal is TRUE, the output displays as .

If the signal is FALSE, the output displays as

If the state of the signal (TRUE/FALSE) is unknown, the output displays as

Note UC2000 runtime software version V03.05.03 provides the state of the signal.This symbol is replaced by the symbol for TRUE or FALSE as shown above.


Diagnostics ExamplesThe examples in this section describe the three diagnostic modes, FAULTED, LIVEand FILE for a task running in the UC2000. The following screen displays the Devicewindow of the UC2000. The name of the UC2000 device is docuc. It has one task,named task1.

UC2000Device

Task

Blocks


There are three BENG_D blocks with TRUE outputs connected as follows:

To obtain diagnostics and back-chaining, the REQDIAG (request Diagnostics isTRUE, and both DDIAG (Disable Diagnostics) and DDIAGBD (Disable DiagnosticBack-chaining) are FALSE.

Output of the block 10:_BENG_D is func1\out1

Output of block 20:_BENG_D is func1\out2

Output of block 30:_BENG_D is func1\out3

All output signals in thediagram are Boolean signals.

These three BENG-D blocks solve the following logic:

where

func1\out1 = func1\bool1 * func1\bool2

func1\out2 = ( func1\bool1 * func1\bool2 ) * ~ func1\bool3

func1\out3 = ( ( func1\bool1 * func1\bool2 ) * ~ func1\bool3 ) + ~ func1\bool4

* represents a logical AND

+ represents a logical OR

~ represents a logical NOT


The signals func1\bool1, func1\bool2 and func1\bool3 are defined in the Outline View ofthe UC2000 as follows:

Fault DiagnosticsDiagnostic messages are displayed in DlanView in the color, cyan. Double-click on adiagnostic message to invoke the Diagnose application. The fault diagnostic data isas a relay ladder diagram (RLD).

This RLD is not the exact Control logic used in the UC2000, but is a representationof the minterm and presents the signals that caused the fault to occur. The examplebelow shows how this diagram should be interpreted for FAULTED diagnostics.

In the following RLDs, the states of the signals (TRUE/FALSE) are the actual valueswhen output went FALSE and generated a diagnostic message. For example, inExample 2 below, bool3 is TRUE and bool1 is FALSE even though the logic onlyrequires one of the two terms to be TRUE for out3 to be FALSE.


Examples of Fault Diagnostics

Fault Example 1

The signal func1\out3 goes FALSE in the control logic due to some condition. TheRLD obtained from the fault diagnostics is as follows:

out3 = FALSE

bool2 = FALSE

bool4 = TRUE

Fault Example 2

Signal func1\out3 goes FALSE in the Control logic due to some condition. The RLDobtained from the diagnostics is as follows:

out3 = FALSE bool3 = TRUE

out4 = TRUE bool1 = FALSE


The following screen shows no power flow to the coil.

Power flow to the coil can be restored by making

bool4 = FALSE

bool3 = FALSE

bool1 = TRUE

The following screen shows power flow to the coil.

The power flow to the coil can be interrupted by making

bool1=FALSE

bool2=FALSE

bool3=TRUE


Fault Example 3

Example 3 shows no power flow to the coil.

The power flow to the coil can be restored by making

bool1 = TRUE

bool4 = FALSE

The following screen shows power flow to the coil.

The power flow to the coil can be interrupted by making bool4 = TRUE


Live DiagnosticsThe examples for Live Diagnostics are identical to the FAULT diagnostics, except inthe status bar the DIAGNOSTICS displays LIVE instead of FAULTED. If the statusof the coil (TRUE/FALSE) is not available, a Don’t Know state displays on the coil.

Example of Live DiagnosticsThe following is an example with unknown coil status for LIVE diagnostic.

File DiagnosticsDiagnostic data previously saved in a file can be either in the FAULTED or LIVEmode. The following example, displays the data in the file, FUNC1.STATUS3.dia.

The Status bar indicates that the diagnostic is a FILE mode. The Devicewindow/signal name, FUNC1.OUR3.dia indicates that this data was obtained from a*.dia file.

GEH-6372D GEMIS Tools for CIMPLICITY Chapter 9 DLAN+ Devcom • 113

Chapter 9 DLAN+ Devcom

IntroductionThe CIMPLICITY HMIProduct must be installedbefore this application can beinstalled.

The DLAN+ Devcom application enables the CIMPLICITY HMI system to directlyaccess data on the DLAN+. It provides both feedback signals and commandmessages.

RequirementsTo ensure proper operation, the DLAN+ Devcom application has the followingminimum requirements:

Software

• Windows NT 4.0

• CIMPLICITY HMI Version 3.00

• SDB V03.02.06C

• SDB Utilities V03.03.06C

• GE Control System Toolbox V03.04.00C

Hardware

Refer to the CIMPLICITYHMI manual, GFK-1180 forcomplete PC requirements.

• PCA198 (ARCNET) board (up to four per PC). The catalog number isPDMM1000DPCCSIPCA198. Refer to the section, PCA198 Hardware Settingson page 115.

114 • Chapter 9 DLAN+ Devcom GEH-6372D GEMIS Tools for CIMPLICITY

ConceptsRefer to Appendix A for thecomplete data flow.

The DLAN+ Devcom application provides the interface between the PCA198 board,DLAN+ Driver, and the CIMPLICITY project. The following diagram is a simplifieddata flow for the DLAN+ signals on the CIMPLICITY server node.

CimView

321

Low Pressure Hydraulic Power System

DLAN+ PCA 198ARCNET board

DLANDevcom

CimView

DLAN+ Signals

Signal Details

DLAN+

Driver

PCA 198ARCNET board

PCA 198ARCNET board

PCA 198ARCNET board

DLAN+

DLAN+

DLAN+

CIMPLICITY Server PC Node

SDB Host PC

Can have up to four PCA198 cards per PC

SDB


PCA198 Hardware SettingsThe PCA198 (ARCNET) board jumper locations and DIP switches can be set byreferring to Figure 1 and the appropriate sections described below.

Note The Memory Address, I/O Port, and Interrupt Request settings in thefollowing dialog boxes must not overlap any other board in this PC. To confirm thatthe values used are unique, click Start\Programs\Administrative Tools\Windows NT Diagnostics. Click the tab, Resources. Click the option buttons,IRQ, I/O Port, and Memory.

Figure 1 PCA198 Board

LSB

MSB

SW1

E3 I/O ADDR

1

8

A9 A4

E2 MISC

RDIS

E4 MEM ADDR

E1 IRQ

15 3

PCA198

E5LEN

LSC

ET2

ET1

M10

16K

1L1

1L2

A23 A14

Note - Default jumpers denoted with

Node Address (SW1)This node address must matchthe System Device DLAN+drop number (see GEH-6333GE Control System Toolbox,Chapter 10).

The node address defines the DLAN+ drop number of the PCA198 board. The switchsettings for the node address (drop number) are viewed through the back of theboard. Figure 2 displays the MSB end of the switch closest to the coax connector.Switches in the up position denote a logical 1 and down denote a logical 0. Theswitch positions are numbered from left to right 1 through 8. In Figure 2, the nodeaddress would be 77 decimal, 4D hex.

Figure 2 SW1 Settings

LSB MSB

SW1

1 8


Interrupt Request Setting (E1)The interrupt request (IRQ) (E1) is set by placing a jumper across the two pinsadjacent to the interrupt number desired. The lowest interrupt supported is 3 and thehighest is 15. Suggested setting is 11 or 9.

I/O Port Address (E3)The I/O Port address (E3) is specified in HEX notation. Table 1 displays the possiblecombinations for I/O address. An entry in the column indicates a jumper is inserted.The table is grouped to easily determine the I/O address major and minor HEX value.For example, the HEX address 260 can be translated as follows:

HEX Digit Jumpers Required Column Number

2 A8 1

6 A4,A7 2

0 No Translation, Always 0

Note In Table 1, the light shaded area in Column 1 and 2 are the jumpers for theabove example. The dark shaded area in Column 1 (HEX 4 through F) indicates theHEX values are illegal. The suggested setting is 0x200.

Table 1 I/O Port Address Combinations

HEX Column 1 Column 2

Value A9 A8 A7 A6 A5 A4

0 X X X X X X

1 X X X X

2 X X X X

3 X X

4 X X X

5 X X

6 X X

7 X

8 X X X

9 X X

A X X

B X

C X X

D X

E X

F


Memory Address (E4)The Memory Address ( E4) is chosen similar to the I/O Port, only there are threecolumn groupings. For example, the address 0C8000 can be translated as follows:

HEX Digit Jumpers Required Column Number

0 A20, A21, A22, A23 1

C A17, A16 2

8 A14 3

000 No translation, always 0

Refer to the shaded area in Column 1, 2, and 3 of Table 2.

Suggested Settings: 0E0000 (preferred) or 0C8000

Do not use address 0D0000 or 0DFFFF, which is reserved forthe Mode Logger assembly (if installed on this PC).

Note In Table 2, the light shaded area in Column 1, 2, and 3 are the jumpers for theexample above. The dark shaded area, HEX 4 through F in Column 3, indicates theHEX values are illegal.

Table 2 Memory Address Combinations

Column 1 Column 2 Column 3

HEX A23 A22 A21 A20 A19 A18 A17 A16 A15 A14

0 X X X X X X X X X X

1 X X X X X X

2 X X X X X X

3 X X X X

4 X X X X X X X

5 X X X X

6 X X X X

7 X X

8 X X X X X X X

9 X X X X

A X X X X

B X X

C X X X X

D X X

E X X

F

CAUTION


Using DLAN+ DevcomA License is required at thebeginning of the installation.Refer to Chapter 2.

DLAN+ Devcom application is part of the GEMIS Tools for CIMPLICITY. It can beinstalled with the tools or installed/upgraded as a separate product. (It must bereinstalled, if there is an upgrade in the CIMPLICITY software.)

Note Prior to an install/upgrade, the CIMPLICITY project must be shut down andthe DLAN+ Driver must be stopped .

À To install DLAN+ Devcom

1. Follow the installation steps in Chapter 2.

2. When setup displays the product selection dialog box, choose DLANDevcom w/Dvr from the product list.

3. Enter the Device name of this PC, as entered in the toolbox and posted to theSDB. This entry establishes a one-to-one correspondence between this PC andthe equivalent device name in the SDB.


PCA198 BoardsUp to four PCA198 boards can be installed in each PC. Each board requires thefollowing information:

Each board will automaticallynumber consecutively fromone.

The drop number is set usingSW1 on the PCA198 board.

• Board number.

• Memory address. This must match the base memory address jumper setting E4on the PCA198 board.

• Interrupt request (IRQ). This must match the interrupt jumper setting E1 on thePCA198 board.

• I/O address. This must match the I/O jumper setting E3 on the PCA198 board.

• Network name of the DLAN+ connected to each board. The name must matchthe name posted to the SDB for the PC/network connection.

• Drop number. This must also match the number assigned to this PC/networkconnection in the SDB.

Note The Memory Address, I/O Port, and Interrupt Request settings in thefollowing dialog boxes must not overlap any other board in this PC. To confirm thatthe values used are unique, click Start\Programs\Administrative Tools\Windows NT Diagnostics. Click the tab, Resources. Click the option buttons,IRQ, I/O Port, and Memory.

The following dialog boxes automatically display during software installation for theuser to install the PCA198 board(s).

Note This information must be entered when the DLAN+ Driver is installed for thefirst time or if the system architecture changes, (such as a version upgrade or moreboards are added).

1. From the DLAN+ Board Quantity dialog box, enter the quantity of PCA198boards that are installed. Click Next.


Typical Interrupt ranges arefrom 2 to 15.

The DLAN+ Board Number 1 dialog box is displayed. The board number displaysin the title bar and in the dialog box description.

2. Enter the Memory Address, Interrupt and I/O Port values. Click Next.

Choose toreview previously entereddata.

3. From the DLAN Net Name/Drop Number dialog box, enter the Net Nameand Drop Number for the board number being configured. The drop numbermust match the node address set by SW1.

The board number, Memory Address, IRQ, and I/O Port that was previouslyentered displays in the dialog box. This data must be provided for all boards.

4. (If there is more than one board, the dialog boxes to enter the data for otherboards automatically display.) Click Next.


Installation is now complete. The following dialog box displays and providesinstructions on how to start the DLAN+ Driver.

5. Click OK.

Note The PC should be rebooted the first time the driver is installed to guaranteeproper installation. These steps must be repeated each time the PC is rebooted.

For more information refer toChapter 3, Importing Signalsand Alarms.

The following dialog box describes the signal routing table file naming conventionsand location. This file is required so the DLAN+ Driver can process commandmessages correctly. When the CIMPLICITY HIM project is restarted, the routingtable file is read by the DLAN+ Devcom application.

6. Click OK.


ConfigurationData flow of a UC2000 and a CIMPLICITY HMI Project can move in bothdirections from a UC2000 to the CIMPLICITY HMI Point Manager and CimView asfollows:

1. UC2000 places data on the DLAN+.

2. The data is read in the CIMPLICITY HMI Server PC by the DLAN+ Driverthrough the PCA198 board.

3. DLAN+ Devcom receives the data from the DLAN+ Driver and provides it tothe CIMPLICITY HMI Point Manager.

4. Data is then available to CimView.

If points are changed within the CIMPLICITY HMI system, then the data is obtainedby the CIMPLICITY HMI Point Manager, passed to the DLAN+ Devcom, whichpasses the data to the DLAN+ Driver. The DLAN+ Driver then places the data on theDLAN+. The UC2000 reads the changed data on the next scan of the ACRNETpage.

UC2000PCA198 Board

CIMPLICITY HMI Server

DLAN+ DRIVER

DLAN+Devcom

CIMPLICITY HMI Point Manager

CimView

DLAN+


Setup the CIMPLICITY HMI ServerThe CIMPLICITY HMI Server must be setup as follows:

Manual is the default Startup,but the Device must be startedthe first time the driver isinstalled.

• The PCA198 board(s) must be installed on the CIMPLICITY HMI Server PC(see the section, PCA198 Boards on page 119).

• DLAN+ Devcom and DLAN+ Driver must be installed on the CIMPLICITYHMI Server PC (see the section, Using DLAN+ Devcom on page 118).

• Verify that the Status of the DLAN+ Driver is Started.

À To verify or start the DLAN+ Driver

1. Click Windows Start button, Settings and click ControlPanel.

2. Double-click the Devices icon. .

3. Scroll down to the ARCNET device. The Startup column should be Manual.The Status column should read Started. If it does not, click on ARCNET (to

highlight the device) and then click .


À To change the Startup method (from the default Manual)

1. Click the ARCNET device and click .

2. Choose a different Startup Type from the following dialog box and click OK.

À Verify that CIMPLICITY HMI Project can see DLAN+ Devcom

1. From the CIMPLICITY HMI Project cabinet, choose the Project menu andthe command Settings...

2. Choose the tab, General.

3. In the option box Protocols, verify that the DLAN+ box contains an X.

To choose thisdialog box, choosethe Project menuand the commandSettings…

Click on the box to select the DLAN+Protocol (box shouldcontain an X).


Setup the UC2000Resources are defined in theSystem Device.

All signals that communicate across the DLAN+ are defined in the GE ControlSystem Toolbox. They are defined in the Outline View, under the item I/O andDisplay Definitions and DLAN+ Interface.

Resource items are defined inthe System Device. When abind is performed, they appear

under the item System Data.

Edit the point to define theData Type and Direction

For more information, referto GEH-6333B, Chapter 10.

In the UC2000, each signal must be defined, including Data Type, Direction, andResource.

À To insert and define a signal in the UC2000

Additional points can beinserted and modified fromthis dialog box.

Resources display in theUC2000 hierarchy under theitem, System Data.

1. From the Outline View, click on a Status_S page (to highlight it).

2. Click again with the right mouse button and choose Insert First.

3. The Point Edit dialog box displays. Define the Data Type (such as float, int),Direction (such as Feedback, Command, or Event), and Resource.

The Resource is defined in the toolbox in the System Device. Then, the signalsare posted to the SDB. Perform a bind for the Resources to appear in the UC2000.


Setup the CIMPLICITY HMI ProjectBefore importing the UC2000 signals, all Resources, Ports, and Devices must bedefined and listed in the CIMPLICITY HMI Project. The following section providesprocedures that define each function.

Resources

Resources (also known as groups) can be devices, machines, or stations where workis performed, or areas where several tasks are carried out. Resource functions filterthe data that users receive and route alarms to specific users.

CIMPLICITY HMI uses Resources as follows:

• Provides a view of the facility defined by the Resources configured for that user.

• Each CIMPLICICTY device and point is associated with a Resource.

• Many base system functions (such as Alarm Viewer) and product optionfunctions use Resource to filter data.

Resource Configuration

À To configure a Resource

To edit this option box, fromthe View menu, chooseOptions…

w From the CIMPLICITY HMI project cabinet, double-click on the

Resource icon. The Resource - Configuration window displays.

Note If the option box Display search criteria at startup is checked, thefollowing dialog box displays at startup and allows the user to create a filtered list ofResources.– Or –Do not check the box and all configured Resources will display in the window.

ä


For more information, referto the CIMPLICITY manual,GFK-1180, Base Systems.

The Resource - Configuration window can display the following attributes for eachResource. The following attributes can be added or removed (except the attributeResource always displays in the Resource - Configuration window).

Resource Name that uniquely identifies each Resource.

ResourceType

Identifies the type of resource, either System or Resource. This isa display only field and cannot be modified.

Description Provides more information about the Resource.

Alarm Mgr Identifies the Alarm Manger process that will receive alarms forthis Resource. This is a display only field and cannot be modified.

The attributes (exceptResource) can beadded or removed.

Choose Attributes fromthe Edit menu todisplay this dialog box.

Create New Resource

À To create a new Resource

1. Choose File menu and New. The New Resource dialog box displays.

3. Enter the Resource ID, such as All.

4. Click OK. The Resource Definition dialog box displays and must be defined.


5. Users for this Resource is the list of users currently assigned to thisResource and can view alarm or signal/point information for this Resource.Choose to add/delete users, view/modify user properties, or create new users.Users not assigned to this Resource display in Available Users text box.

6. In the Description text box define the Resource, using up to 40 characters oftext (cannot use $ or | characters).

7. Click OK. The new entry displays in the Resource - Configuration window(see previous window).


✔

Ports

For more information, referto the CIMPLICITY HMImanual, GFK-1181- BaseSystems.

A port is an interface that synchronizes the flow of data between the CPU andexternal devices such as a UC2000. Configuration requirements for ports varydepending on the type of port and communications protocol being used. Thefollowing procedure configures ports and specifies their characteristics.

Port - Configuration

À To configure a Port

w From the CIMPLICITY HMI project cabinet, double-click the Ports icon.The Port - Configuration window displays.


Note If the option box search criteria at startup is checked, the followingdialog box displays at startup and allows the user to create a filtered list of Ports.– Or –Do not check the box and all configured Ports will display in the window.


The Port - Configuration window can display the following attributes for each Port.The following attributes can be added or removed from the window (except theattribute Port always displays in the Port - Configuration window).

Port Identifies the name of each Port.

Protocol ID Identifies the protocol used for device communications.

Description Provides more information about the Port.

Alarm Mgr Identifies the Alarm Manger process that will receive alarms for thisResource. This is a display only field and cannot be modified.

The attributes(except Port) can beadded or removed.

Choose Attributesfrom the Edit menuto display thisdialog box

Create New Port

À To create a new Port

1. Choose File menu and New. The New Port dialog box displays.

2. Choose the Node name of the PC where the port is located (if applicable).

3. In Protocol, choose Status_S from the drop-down list. (Protocol isdetermined by the node that was chosen and the protocols available.)

4. Choose a Port from the drop-down list (either ARC0, ARC1, ARC2, or ACC3).Port is determined by the node and protocol that was chosen.


5. Click OK. The Port Properties dialog box displays and must be defined.

Note The field Protocol was defined when the new port was created. To changeProtocol, see the next section Changing a Port’s Protocol.

6. Enter a Description using up to 40 characters to describe the port.

7. Enter a Scan Rate for points monitored from this port. The scan rate can be setin units of Ticks, Seconds, Minutes, or Hours.

8. Enter a Retry Count for the number of times to retry communications todevices on this port after a communication error is encountered.

9. Check Enable to maintain communications on this port.

10. Click OK. The new entry displays in the Port - Configuration window.

Changing a Port’s Protocol

À To change the Port Protocol

For more information on theImport/Export utility, refer tothe section Importing Signalsand Alarms, in Chapter 3 onpage 29.

1. To re-use the same point data, export the point data for the Port using theImport/Export utility

2. Delete the point data for the Port.

3. Delete the device data for the Port.

4. Delete the Port.

5. Create the Port with the new Protocol.

6. Define the devices for the Port.

7. If the point data was exported, use Import/Export utility to import the point data.Otherwise, define new points.


Device

Configuration requirementsfor devices vary depending onthe type of device andprotocol used.

A device communicates signal/point data to CIMPLICITY HMI software.CIMPLICITY HMI can read data from and write data to devices, such as theUC2000. The following procedure configures the UC2000 and specifies itscharacteristics.

Device Configuration

À To configure a Device

1. From the CIMPLICITY HMI project cabinet, double-click the Devicesicon. The Device - Configuration window displays.


Note If the option box, Display search criteria at startup is checked, thefollowing dialog box displays at startup and allows the user to create a filtered list ofDevices.– Or –Do not check the box and all configured Devices will display in the window.

ä


Refer to the CIMPLICITYHMI manual, GFK- 1180Base Systems.

The Device - Configuration window can display the following attributes for eachDevice. These attributes can be added and removed (except the attribute Device IDalways displays in the Device - Configuration window)..

Device ID Identifies the name of each device.

Port Identifies the port that the device is connected.

Description Provides more information about the device.

Resource Is a configured Resource. Only users that are assigned thisResource can view alarms for this device.

The attributes (exceptDevice ID) can be addedand removed.

Choose Attributes fromthe Edit menu todisplay this dialog box.

Create New Device

À To create a new device

1. Choose File menu and New. The New Devices dialog box displays.

2. Enter the Device name. It is the same as the UC2000 device name for theEthernet with _D added, such as UC12_D.

3. Enter the name of the Device’s Port (MASTER_ARC0).

4. Click OK. The Device dialog box displays and must be defined.


5. From the General tab, enter a Description of the device using up to 40characters.

6. Enter the device’s Resource. Only the users that are assigned this Resource cansee device alarms.

7. In the Model Type drop-down list choose DLAN. (The list of model typesdepends on the Protocol).

8. Click the Default tab and enter the Address. The address is the Name of theDLAN+ that this device is connected to.

9. Click OK. The Device displays in the Device-Configuration window.


Users

The User function configures Users for the CIMPLICITY HMI software. Eachindividual user has the following attributes:

The default configurationincludes, User ID:ADMINISTRATOR and RoleID: SYSMGR.

The default user does notrequire a password to accessCIMPLICITY MHI softwarefunctions.

Security enables the user to be assigned a Password. The user must enter both theUser ID and password to access CIMPLICITY HMI.

Roles are assigned to each user. Each role has certain privileges that define thefunctions the user can access. If a user lacks the privilege to access a securefunctions, an error message displays and access is denied.

View of Resources determine the Resource data that the user has access. Alarms forresources outside a user’s view does not appear on the user’s Alarm Viewer window.

User Configuration

À To configure Users

1. From the CIMPLICITY HMI project cabinet, double-click on the

Users icon. The Users Properties dialog box displays.


Note If the option box, Display search criteria at startup is checked, thefollowing dialog box displays at startup and allows the user to create a filtered list ofUsers.– Or –Do not check the box and all configured Users will display in the window.

ä


Refer to the CIMPLICITYHMI manual, GFK-1180.

The User - Configuration window can display the following attributes for each user.These attributes can be added and removed (except the attribute User ID alwaysdisplays in the User - Configuration window).

User ID Identifies the name of each User.

Password Displayed in this field (if defined).

Role ID Determines the privileges assigned to the user.

User Name Is the user’s name.

Attributes (except UserID) can be added andremoved.

Choose Attributes fromthe Edit menu to displaythis dialog box.

Create New User

À To create a new User

1. Choose File menu and New. The New User dialog box displays.

2. Enter the name of the new user. Click OK. The User Properties dialog boxdisplays.


3. From the General tab, enter the user’s Role.

4. If a password is desired, check ä Password Needed and enter a passwordand then confirm the password.

5. Enter the User’s name or a description.

6. Click on the Resources tab. Define the resources that the user can viewalarms. The resources currently assigned to the user are displayed in theResources box.

7. Resources can be added or deleted. Click OK.


Setup the SDB UtilitiesRefer to Chapter 3, SDB Utilities for proper setup of the CIMPLICITY Server.

1. From the SDB Utilities, check that the DLAN+ is listed under the items,CIMPLICITY Server and Net Connections.

2. If it is not listed, insert the DLAN+ by choosing the Edit menu and InsertNet… (see page 23).

The Edit NET Connections dialog box must be defined, including NetName, Net Type , Drop Number , Board Number , and Page Number .

3. Import the Control System Toolbox signals into the CIMPLICITY HMI project(see Appendix B, System Level Activities Required To Import Signals into theCIMPLICITY HMI Point Database).

4. From the CIMPLICITY HMI project cabinet , click the Points icon tocheck that the signals were imported properly.


UninstallÀ To remove the DLAN+ Devcom product

1. Choose Start\Settings\Control Panel\ and the icon Add/RemovePrograms.

2. From the tab, Install/Uninstall, click GE DLAN+ Devcom

3. Click Add\Remove button.

Removal of the DLAN+ Driver is unconditional. Any applicationsusing this driver will terminate.

À To remove the DLAN+ Driver

1. Insert the installation Disk 1 for the GEMIS Tools for CIMPLICITY or locatethe file for Disk 1 on the network.

2. Run setup.

3. In the Product Selection dialog box, choose DLAN Driver Only and Next.

4. Setup determines that DLAN+ Driver is already present. Choose the optionRemove DLAN+ Driver.

CAUTION


TroubleshootingThere are two utilities supplied with the DLAN+ Devcom to help troubleshootingthe DLAN+ Driver and DLAN+ Devcom subsystem:

Arcuty displays information about the DLAN+ Driver. The executable name isarcuty.exe

Siguty displays the symbol resolution cache used by the DLAN+ Devcomapplication. The executable name is siguty.

These utilities do not have program icons under the GEMIS Tools for CIMPLICITYprogram group. They must be executed using Windows NT Explorer and are locatedin the directory C:\GEMIS-MMI\support.

GEH-6372C GEMIS Tools for CIMPLICITY Chapter 10 DLAN+ Status Monitor • 141

Chapter 10 DLAN+ Status Monitor

IntroductionThis chapter describes the DLAN+ Status Monitor application, which is used to viewthe status of drops on a particular DLAN+. DLAN+ traffic can also be displayed on aper drop basis. The DLAN+ Status Monitor can display the drop status as a functionof devices defined in the SDB.

ConceptsThis application provides a graphical display of the drop data written to the MessageArchiver Database by the Message Archiver Service. The DLAN+ Status Monitorcan access any Message Archiver database that is either local to the machine or existsin a directory mapped to the local machine.

142 • Chapter 10 DLAN+ Status Monitor GEH-6372C GEMIS Tools for CIMPLICITY

The following diagram shows the data flow in the system.

ModeLoggerPC 1

MessageArchiver

Database

MessageArchiver

DLAN+ Messages

DLAN+Messages

DLAN+ Network A

SDB

PCLG Assembly



Within a single PC

ModeLoggerPC 2


DLAN+ Network B

PCLG Assembly

DLAN+Status

Broadcast and directedmessage counts are written inbytes.

Timestamp is a value thatspecifies the time data wascreated, modified, accessed,or received.

The Message Archiver periodically writes the drop link presence status, broadcastmessage count, and the directed message count for each drop on the DLAN+ to theMessage Archiver Database. The DLAN+ Status Monitor reads the data, calculatesthe appropriate data rates for each drop, and updates the display. Timestamp data,located in the Message Archiver Database, determines if the data is being activelyupdated (Live).

The drop link presence status can be displayed against the device definitions in theSDB. The SDB location is read from the Message Archiver Database and the systemtopology is read from the SDB by the DLAN+ Status Monitor application. Thefollowing table defines the status of the displayed drop by the background color.

Drop Status BackgroundColor

Defined active drops Green

Undefined active drops Yellow

Defined Inactive drops Red

Inactive drop Black

No current data (not updated by the MessageArchiver for at least two data samples)

Gray

Note The SDB location cannot be set by the user. The SDB server name and pathare read from the Message Archiver Database to ensure that the Message Archiverand DLAN+ Status Monitor application are using data from the same SDB.


Grayed out data indicates that Mode Logger is not running or Message Archiver iseither not running or not sending messages to the database being accessed byDLAN+ Status Monitor, or DLAN+ is unresolved.

DLAN+ Status Monitor can be used without access to an SDB. All functions areavailable except the Database Drop Status mode, which reports all live drops asundefined. Message Archiver will populate the DLAN+ tables even if the SDBconnection cannot be made, however, the DLAN+ name will not be correct.

Using DLAN+ Status MonitorDLAN+ Status Monitor can display data for any DLAN+, provided the location ofthe Message Archiver Database is known and the Mode Logger is either local to themachine or is mapped to it. The following sections describe the menu commands andtoolbar shortcuts used to configure the application.

Menus Commands

Settings Menu

The Settings menu has the following commands. Refer to the section, Configuration.

Database... allows the user to choose the path of the Message Archiver database.

DLAN+... allows the user to choose which DLAN+ to display from MessageArchiver Database.

Display Size... allows the user to change the font and window size of the display.


Display Menu

The Display menu has the following commands.

These commands can also be accessed from the toolbar:

Click To display

Database Drop Status, the link presence status of each drop in relationto the devices defined in the SDB.

Drop Status, the link presence status of each drop on the chosenDLAN+.

Drop Total Rate, the combined broadcast and directed data rates foreach drop on the DLAN+.

Drop Broadcast Rate, the rate of broadcast messages for each drop onthe DLAN+.

Drop Directed Rate, the rate of directed messages for each drop on theDLAN+.

Drop Total Count, the combined broadcast and directed messagecount for each drop.

Drop Broadcast Count, the broadcast message count for each drop onthe DLAN+.

Drop Directed Count,the directed message count for each drop on theDLAN+.


ConfigurationThe following commands are in the Settings Menu.

Database LocationÀ To configure the Message Archiver Database location

1. From the Settings menu, choose Database... The Message ArchiverDatabase location dialog box displays.

2. Enter the path of the message database or use Browse to locate the database.

3. Click OK.

DLAN+…Multiple DLAN+s can be represented in a single Message Archiver Database table.

À To choose a DLAN+ from the existing Message Archiver Databasetable

1. From the Settings menu, choose DLAN+... The Available DLAN+s dialogbox displays.

2. Choose a DLAN+ from the list box and click OK.


Display SizeThe Display Size command can maximize or minimize the screen size used by theDLAN+ Status Monitor window.

À To edit the Display Size

1. From the Settings menu, choose Display Size… The Display Size dialogbox displays.

2. Click the option button for the desired size of the screen display and click OK.

Status BarThe Status bar displays the current program configurations as follows:

Name of current DLAN+ Message Archiver Database location Name of SDB Server node is in [ ] and SDB location

Troubleshooting

Mode Logger Controlmanages the starting andstopping of the Mode Loggerand Message Archiver.

The DLAN+ Status Monitor displays the DLAN+ data that is periodically written tothe Message Archiver Database by the Message Archiver service. It must alsocompare that data with topology information read from the SDB when DatabaseDrop Status mode is active. Therefore, it is necessary to make the correct connectionto the Message Archiver Database and the SDB.

The Mode Logger Control application manages the Mode Logger and MessageArchiver services. It can resolve issues where the DLAN+ Status Monitor cannotconnect to the Message Archiver Database or is not displaying Live data. Use theSettings menu to determine the current configuration of the Mode Logger andMessage Archiver services and to change their configuration.


Refer to the following table for troubleshooting procedures:

Problem Procedure

Location of the MessageArchiver Database for aparticular DLAN+ network isnot known

1. Locate and run the Mode Logger Control on the PC connected to the DLAN+ todetermine where the raw Mode Logger messages are being sent. (From the ModeLogger control, click Setting and the Mode Logger tab. Determine the destination fothe Mode Logger messages from the option box Send Mode Logger messages toArchiver either This PC or Remote PC.)

2. From the PC that is specified as the destination of the Mode Logger messages, runMode Logger Control (step 1), and check the Message Archiver tab for specifiedMessage Archiver Database Location.

3. If the Message Archiver Database is not local to the PC containing DLAN+ StatusMonitor, map to the directory (using Explorer) where the Message ArchiverDatabase resides.

4. Start DLAN+ Status Monitor. It will automatically attempt to connect to the last validMessage Archiver Database that it was connected to or it will prompt the user forthe Message Archiver Database location if it has never been run on the PC before.

5. Enter the Message Archiver Database location either at the prompt or from theSettings/Database dialog box. DLAN+ Status Monitor will automatically begindisplaying the first DLAN+ network it finds in the Message Archiver Database. If adifferent DLAN+ is to be displayed, from DLAN+ Status Monitor choose theSettings menu and DLAN+…

Set the SDB server name andpath

The SDB server name and path are read from the Message Archiver Database andcannot be set by the user. This is done to keep the topology data displayed by DLAN+Status Monitor consistent with the Message Archiver data.

Data is displayed against agray background. (Why isn’tthe data live?)

Possible causes:

The DLAN+ Status Monitor application compares the current data timestamp with theprevious data timestamp to determine if new data is being read from the MessageArchiver database. If the timestamp changes between successive reads from thedatabase, the data read is considered Live, and is displayed against a greenbackground (possibly red or yellow in Database Drop Status mode ).If the timestamp does not change between successive reads, the data for the currentlyselected DLAN+ is not being actively updated by the Message Archiver service anddisplays against a gray background.

Message Archiver is not receiving data from Mode Logger (refer to Chapter 4).

1. Verify that Mode Logger is running (check Mode Logger status in the Mode LoggerControl application).

2. From the PC where Mode Logger is running, check the Mode Logger settings. Thelocation should correspond to the location of the Message Archiver Databasedisplayed by DLAN+ Status Monitor.

3. From the PC where Message Archiver is running, check the Message Archiversettings. The Message Archiver Database location should correspond to thelocation of the Message Archiver Database displayed by DLAN+ Status Monitorstatus bar.

Message Archiver is not running.

w Check Message Archiver status in the Mode Logger Control program.


Problem Procedure

Possible cause — continued Message Archiver is not updating the selected database.

w Refer to the following problem, Where is the Message Database for a particularnetwork?

Message Archiver is not updating the data for the currently selected DLAN+.

w Refer to the following problem, Why are there more DLAN+ entries in the DLAN+list than there are DLAN+ networks in the system?

There are more DLAN+entries in the DLAN+ list thanthere are DLAN+s in thesystem

Message Archiver was unable to connect to the SDB at some point when it started up,creating a duplicate DLAN+ entry. Message Archiver relies on the SDB to resolve theDLAN+ names based on the DLAN+ number included in the raw Mode Loggermessages. Message Archiver uses the SDB topology to determine the DLAN+ name. IfArchiver cannot contact the SDB, it defaults the DLAN+ name to NET_X, where X is theDLAN+ Net Number specified by the user in the Mode Logger Control application underthe Settings menu/Mode Logger page. Message Archiver creates an entry (by name) inthe Message Archiver Database for the DLAN+ if it does not already exist whenMessage Archiver is started up. If SDB is unavailable when Message Archiver is startedup, multiple entries for the same network may exist in the Message Archiver Database.Only one of those network entries is updated by Message Archiver at any one time,depending on the state of the SDB connection when Message Archiver was started.

Delete the redundant network entries by:

• Stopping Message Archiver and the entire Message Archiver DatabaseOr

• Stopping Message Archiver and using the Browse utility to delete the redundantentries from the NETSTAT.DBF table.

DLAN+ names are incorrect,for example ALAN is listedas NET_1

SDB is not specified correctly in the Message Archiver setup, causing the networknames to be defaulted to Net_X. Refer to the previous problem, Why are there moreDLAN+ entries in the DLAN+ list than there are DLAN+s in the system.

Drop names all display asUNDEF in Database DropStatus mode

All live drops on the DLAN+ that do not have a corresponding device listed in the SDBtopology are labeled as undefined. If the DLAN+ Status Monitor application cannotconnect to the SDB, all of the live drops will be labeled as undefined.

Some of the data fieldsdisplay roll instead of anumber

Some versions of Mode Logger application do not correctly represent the data when theMode Logger board’s data values roll over. Rather than starting over at zero, the valuesbecome large negative numbers. Rather than display confusing and inaccurate data onthe screen, the DLAN+ Status Monitor application displays roll, where a negative valueis encountered. The Mode Logger Board’s register values can only be reset by restartingthe Mode Logger service, either through the Mode Logger Control or by rebooting thePC.

Err displayed in some of thedata fields

Err displays if the value of a particular data field is too large to be displayed by DLAN+Status Monitor (such as >999G ). This should never happen because the Mode Loggerdata register will roll over long before a number that large occurs. However, the data inthe Message Archiver Database would be suspect in this case.

GEH-6372D GEMIS Tools for CIMPLICITY Appendix A CIMPLICITY HMI • 149

Appendix A CIMPLICITY HMI

IntroductionCIMPLICITY HMI contains Windows NT applications and services for monitoringand control of industrial equipment. These applications are configured in aserver/viewer architecture. The server collects and distributes the data with thecontrollers. The viewers present the data in various ways and also provide ways tosend data back to the controllers. The following drawings show these functions.

Point Mgr

SRTPDEVCOM

Initialization andonline configuration

Initialization andonline config

Offline PointDatabase

Ethernet(runtime)

AlarmMgr

Alarm/EventSQL

Database

AlarmConfiguration

Points In Alarm

Ethernet

Alarm MgrInterface

DLAN+ Alarms/Events

AlarmAPI

AlarmLogger

Logged Alarm/Event

Logged Alarm/Event

Device in Alarm

HistoricalPoint SQLDatabase

PointData

Logger

Logged Alarm/Event

Logged Points

Trend in CimVIEW viaEthernet

Ethernet

CIMPLICITY HMI Server

Point DataEthernet Interface

withMessager Archiver

GE Fanuc

GE Motors & Industrial Systems

150 • Appendix A CIMPLICITY HMI GEH-6372D GEMIS Tools for CIMPLICITY

MessageArchiveDatabase

Alarm DLAN+ Messages

CIMPLICITY HMI Viewer

with Mode Logger

AnimationData

PointShopping

List

CommandSetpoints

Tension

CimReport CimView

DLAN+ MessageDatabase

AlarmView

Alarms/EventsAcknowledged

Alarms

DLAN+Historical

AlarmEvent

OperatorAlarms

ModeLogger

DLAN+

Alarm Manager Interface viaEthernet

SystemDatabase, (can

be remote)

Ethernet

MsgArchiver

Signal Information for DLAN+ Messages

GE Fanuc

GE Motors & Industrial Systems

PCLGBoard

GEH-6372D GEMIS Tools for CIMPLICITY Appendix A CIMPLICITY HMI • 151

The following figure and table is an example of the minimum requirements for system architecture.

MessageArchiverDatabase

SDBGECAMS

CIMPLICITY ALARMMANAGER

DLANStatCimReport Diagnose

Mode Logger

PCLG Assembly

Shared Memory

Direct DLAN+Connection

TCP/IP WindowsSocket

Microsoftnetworking

Local API Calls

MessageArchiver

CodebaseAPI

CIMPLICITY

Alarm API

CodebaseAPI

CodebaseAPI

CodebaseAPI

DLAN+ Net BDLAN+ Net A

UC2000

Mode Logger

PC3

PC1 PC2

PC4

CIMPLICITY Server

PCLG Assembly

Shared Memory

PC5

SDBUtility

Install the following programson the PC checked

PC1 PC2 PC3 PC4 PC5

PCLG Assembly ä äMode Logger ä äMessage Archiver äMessage Archiver Database äSDB äSDB Utility äDlanView äDiagnose äDLAN+ Status Monitor äDLAN+ Devcom äGECAMS äCIMPLICITY Alarm Manager äCIMPLICITY Server ä

152 • Appendix A CIMPLICITY HMI GEH-6372D GEMIS Tools for CIMPLICITY

Access viaCIMPLICITY pointid

WinNT/ CIMPLICITY Server

WinNT /SDB -- L1 file server

CIMPLICITY PTMGR

PTConfiguration

Utility

GE_DLANDevcom

Fanuc standard routines

Metals"user"

routines

point id

DLAN+ Status_SShared Memory

WinNTARCNET

Driver

F0 write messages

Reads/local Writes

signalattributes

SDB

SDBServer

signalattributes

lookup bysignal name

CimView/CimEdit

Winsocketconnection:

registry entrys: :

SDB HOST NAMESDB PATH

CIMPLICITY GE_DLAN+Devcom Data Flow

Point_DB

SymbolsGlobal Section --Shared Memory

(loaded via "user_init" inDevCom)

symbols cacheregistry entry:

DLAN SYMBOL TABLE FIL

attributes(@DevCom startup)

siguty(interactive

utility)

SDB Utilities &"clie import"

routingtable

@DevCom startup(by user_open_port)

GE ControlSystemtoolbox

interactiveutility

routing data

during system

configuration

GE DLAN Devcom:

Manual operationrequired during systemdevelopment for "bulk"signal uploads

signalrequests

(if lookup fails)

user validate point

CLIE import (.csv) file

signals & topology(posting)

ArcUty(interactive utility)

User must attach"RESOURCE" to signal

DLAN+ Signal =CIM point_id

%r,%m,x.y =CIM address

GEDS device + _D=CIM device

Drive configuration, downloads,etc., are not supported via theWinNT ARCNETdriver - aUC2000 is required.

GEH-6372D GEMIS Tools for CIMPLICITY Appendix B SDB Utility Detail Information • 153

Appendix B SDB Utility Detail Information

DLAN+ Configuration Registry DataThe DLAN+ Configuration Registry Data is stored in the registry under:HKEY LOCAL MACHINE hive key:

SYSTEM\CurrentControlSet\Services\ArcNet\AnetCard<n>

where

<n> is the number of the card (between 1 and 4)

For each PC198 board there are three registry values:

The page rate is fixed at 1000ms and the size is fixed at onesixteen word block.

• Page_CFG (REG_SZ) <ppp> <rrr> <ss>

where

<ppp> is the page number

<rrr> is the page rate

<ss> is the size in 16-word blocks

There are other values foreach board, which are setonly when the DLAN+Devcom is installed

• Net_name (type REG_SZ)

• SoftLinkAddr (drop number)

The following example is for two boards. Board 1 has a page number of 14, a pagerate of 1000 ms, and one 16-word block. The network name is FDL01 and the dropnumber is 101. Board 2 has a page of 20, a page rate of 1000 ms, and one 16-wordblock. The network name is FDL02 and is at drop 102.

SYSTEM\CurrentControlSet\Services\ArcNet\AnetBoard1

Key name 1 = Page_cfg

Key value 1 = 14 1000 1

Key name 2 = Net_name

Key value 2 = FDL01

Key name 3 = SoftLinkAddr

Key value 3 = 100

154 • Appendix B SDB Utility Detail Information GEH-6372D GEMIS Tools for CIMPLICITY

SYSTEM\CurrentControlSet\Services\ArcNet\AnetBoard2

Key name = Page_cfg

Key value = 20 1000 1

Key name 2 = Net_name

Key value 2 = FDL02

Key name 3 = SoftLinkAddr

Key value 3 = 101

From the above registry information, the SDB Utilities fixes the data rate to 1000 msand a page size of 16 words. The page number, net number, and drop areconfigurable through the SDB Utility.


Example Routing TableThe following is an example routing table with an explanation of each field:

!! This is the Device Routing Data for device (CHMI) (DevNo 1055)! for DLAN (DLAN = 2) on drop (3)! 07/01/97 15:17:40!! ----- PRIMARY ------- --- SECONDARY ----!QNX_ID dev_no net_driver bridge_addr net_driver bridge_addr!------ ------ ---------- ----------- ---------- ----------- -1 552 ARC 1 ARC 1 -1 1000 ARC 2 ARC 2 -1 1055 SELF -2 SELF 3 -1 1054 ARC 4 ARC 4 -1 1057 ARC 5 ARC 5 -1 1056 ARC 7 ARC 7 -1 551 ARC 2 ARC 2 -1 -2 ARC 0 ARC 0 -1 -1 ARC 2 ARC 2

QNX_ID is currently not used.

Dev_no is the unique ID number for a device. Negative numbers indicate a networknumber.

Net_driver is either ARC or SELF. See notes below.

Bridge_addr is the drop number used to get a command message to the givendevice identified by the device number. See notes below.

Primary is the major route for sending commands to the device.

Secondary is the minor route for sending commands to the device. If there is onlyone route, then Secondary bridge_addr equals primary bridge_addr.

Notes

• If there is only one possible route for a command, then primary bridge_addris equal to secondary bridge_addr and bridge_addr is the drop numberused to route the message.

• If net_driver is SELF, (for whom the table is created) then the primarybridge_addr is the negative net number of the network to which SELF isconnected and the secondary bridge_addr is the drop of SELF on thisnetwork.

• If net_driver is ARC and bridge_addr is greater than zero, then thebridge_addr is the drop number used to route the command.

• If net_driver is ARC and dev_no is less then zero and bridge_addr is equalto zero, then the command is to be broadcast on the network identified underdev_no.

• If net_driver is ARC and dev_no is less then zero and bridge_addr isgreater than zero, then send a command to the drop identified underbridge_addr, which is then to be broadcast by that device onto the networkidentified under dev_no.


Mapping Between an SDB Signal and a CIMPLICITY HMIPoint

The following table shows how SDB signal data is mapped to a CIMPLICITY HMIpoint during an import.

Point/Signal Mapping

SDB Signal CIMPLICITYHMI PointDatabase

Point Database FieldDescription

Assigning Point Database Fields from SDB

SIG_NAME PT_ID Unique name for a point. One for one

SIGADDR ADDR Address of point within adevice. For devices withmemory types, this fieldcontains the memorytype.

For ETHR_SRTP: SDB address is in the form%R0023 or %M0034.12 (Boolean). If theaddress is %R, then ADDR = SIGADDR. Ifaddress is %M, then ADDR is %M, plus thenumber to the left of the decimal (%M0034)

For DLAN+: The address is the DLAN word andDLAN bit number separated by the characterperiod (.) For example, 3.2 is word 3, bit 2. If thePoint is a none bit, then it is just the wordnumber ( 45 == word 45)

SIGADDR ADDR_OFFSET Offset in memory fromthe first bit of the Pointaddress. For analog,APPL, text point types,this field must be zero.

For ETHR_SRTP: If %R, then ADDR_OFFSETis zero. If %M, then ADDR_OFFSET is numberto the right of the decimal (12)

For DLAN+: Set to 0.

DEV_NAME DEVICE_ID Device where point dataoriginates. Must be aconfigured Device IDprior to import.

For ETHR_SRTP: One for one. In the SDB, thisis the five character name for the device thatowns the signal.

For DLAN+: The characters _D are appended tothe SDB Device name to obtain the DEVICE_ID.For example, the SDB Device name UC1becomes UC1_D. The CIMPLICITY DEVICE_IDmust be unique.

SIG_DIR ACCESS Direction of data flow forthe signal.

SIG_DIR = R (read) -> ACCESS = R

SIG_DIR = W (write) -> ACCESS = W

SIG_DIR = B (both) -> ACCESS = W

RES_ID RESOURCE_ID Resource ID for point.Must be a configuredResource ID prior toimport.

One for one.


Point/Signal Mapping continued

SDB Signal CIMPLICITYHMI PointDatabase

Point Database FieldDescription

Assigning Point Database Fields from SDBDatabase

(depends onscalinginformation)

ENG_MAX

ENG_MIN

RAW_MIN

RAW_MAX

CONV_TYPE Point engineering unitconversion type. Validvalues:

NO = None

LC = Linear conversion

CS = Custom conversion

If ENG_MIN and ENG_MAX and SRC_MIN andSRC_MAX are defined and data type is REAL,then CONV_TYPE = CS. The option, IncludeScales must also be checked (see Import DevicePoint Options). Otherwise it is NO.

The custom conversion is based on the followingequations:

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

b = (eng_min - src_min * m)

forward equation = "(%p/m + b)"

reverse equation = "((%p - b)*m)"

*UNITS(SCALE)

ENG_UNITS Units that datarepresents.

One for one.

*PRECISION(SCALE)

PRECISION Number of decimalplaces in display.

If defined in the SDB, one for one - Otherwise itis 0 and marked as not used.

ALM_CLASS The Alarm Class ID to beused for the point’salarms. The Alarm ClassID must be defined inCIMPLICITY HMIdatabase prior to import.

If HHIGH or HIGH or LOW or LLOW defined andoption to include alarm data and alarm class ischecked, then ALM_CLASS is as defined in theOptions dialog.

Otherwise it is NONE

SIG_DESC ALM_MSG Text that displays whenthe alarm is set.

If HHIGH or HIGH or LOW or LLOW defined andoption to include alarm data and alarm class ischecked, then ALM_MSG=SIG_DESC

Otherwise it is NONE.

(SCALE)

*HHIGH

*HIGH

*LOW

*LLOW

ALM_HIGH_2

ALM_HIGH_1

ALM_LOW_2

ALM_LOW_1

High alarm limit

High warning limit

Low alarm limit

Low warning limit

If defined in SDB, then one to one and option toinclude alarm data and alarm class is checked.See the section, Import Device Point Options.

Otherwise zero and marked as not used.

SIG_DESC DESC Description of point One for one

DATA_TYPE PT_TYPE Identifies type and lengthof point data. Must be aconfigured point type.

See Data Type table below

* The data for these fields come from the SCALE table of the SDB.

Data Type

SDB Data Type CIMPLICITY HMI Point Type

BIT BOOL

BOOL BOOL

INT, SHORT INT

LINT, LONG DINT

REAL, FLOAT REAL

CHRxx STRING[xx]


Details and Example .csv FilesWhen using the Series 90-70 PLCs, the shared name file (*.snf) is a .csv file thatafter editing can be imported into the Point Database as a .csv file.

SDB Import

CIMPLICITY HMIProject Point

Database

Ethernet

*.CSV File

CLIE Import of *.CSV File

SDB_IMP2.vsd

*.SNF File

Logicmaster 90

MicrosoftExcel

Open with Excel

Save as *.CSV

When the .snf is generated, the following fields are generated for the import:

Logicmaster 90 Field Point Database Field Name

Reference * ADDR

Nickname PT_ID

Description DESC

Length ELEMENTS

Type ** PT_TYPE

Conversion Notes

* A signal that is a blockname produces the address (ADDR) %L1,name. Thismust be changed to %L1name (by removing the comma).

** Timer and PID are not supported point types. Also, %M Booleans are assignedPT_TYPES of integer (INT) in creating .snf files. All %M Booleans need to bechanged from INT to BOOL before importing. Refer to the following examples.


The following is an example of a .snf file. Lines beginning with ## are commentlines. The first non-commented line defines the field names for the data to follow.

##S9070 Device: SAB97

##Output File: Z:\TOOLBOX\TBV3\sab97\SAB97.snf

##Created on: 9/25/96 at 8:54 AM

PT_ID, ADDR, DESC, PT_TYPE

##Page: TO97: %M1 : in

##

ALAN_OK, %M00035, "ALANLINK IS OK", INT

DRY1STP, %M00037, "DRY1", INT

F_UCDO, %M00036, "WRAP AROUND VME COHERENCY BIT", INT

JOGFWPB, %M00033, "JOG FORWARD PUSH BUTTON", INT

To import an .snf file into the CIMPLICITY HMI Point Database, rename it to a .csvfile. The conversion rules noted above must be followed.

##S9070 Device: SAB97

##Output File: Z:\TOOLBOX\TBV3\sab97\SAB97.csv

##Created on: 9/25/96 at 8:54 AM

PT_ID, ADDR, DESC, PT_TYPE

##Page: TO97: %M1 : in

##

ALAN_OK, %M00035, "ALANLINK IS OK", BOOL

DRY1STP, %M00037, "DRY1", BOOL

F_UCDO, %M00036, "WRAP AROUND VME COHERENCY BIT", BOOL

JOGFWPB, %M00033, "JOG FORWARD PUSH BUTTON", BOOL


Mapping Between SDB Alarms and CIMPLICITY AlarmSDB Alarm CIMPLICITY

HMI AlarmCIMPLICITY Field Description Assigning CIMPLICITY Fields from SDB

GROUPNAME+

ALARM INDEX or

DEVICE_TRP or

DEVICE_FLT

ALARM_ID Unique name for an alarm. SDB Broadcast alarms: The ALARM_ID is theconcatenation of Broadcast group name andthe alarm index number.

Standard Device Alarms: ALARM_ID is theconcatenation of Devic name and _TRP or_FLT.

class_id class_id Alarm Class Broadcast alarms: user-defined

Standard Device alarm: “DFLT”

alarm_type_id Alarm types are useful to defineand refer to common types ofalarm messages.

Alarm type fixed at “AMSI_ALARM”

alarm_msg alarm_msg Actual text for the alarm. Broadcast alarms: user-defined

Standard Device alarms: defined by device.

del_opt del_opt Under what conditions an alarmcan be deleted from the alarmqueue. Delete on Reset orAcknowledge or both.

Broadcast alarms: user-defined

Standard Device alarms: fixed at Acknowledgeand Reset.

manual_clear_allowed

manual_clear_allowed

Can the user manually clear thealarm?


Standard Device alarms: fixed at ‘Yes’.

log_opt log_opt Logging option: log on any orall: alarm generated,acknowledged, reset, delete.

Fixed at Log on Generation and Log on Reset.

ack_tout ack_tout Condition for AutoAcknowledge: Never,Immediate, Timed


Standard Device alarms: Never

clr_tout Condition for Auto Clear (reset):Never, Immediate, Timed

Fixed at ‘Never’

rep_tout Condition for Auto Repeat ofalarm to interested processes:Never, Immediate, Timed

Fixed at ‘Never’

max_stacked Define the number ofoccurrences to retain when thisalarm is generated more thanonce before being deleted. Afterthe Max Number Stacked isreached, the oldest alarmoccurrence is deleted as eachnew occurrence is generated.

Fixed at 0

help text help_fname File name that contains the helpfor this alarm

Broadcast alarms: Help file name is fixed at:alarm_id.txt . Alarm help defined in the ToolboxSystem Device.

Standard Device alarms: none.

log_file log_file Log alarm? If yes to log file orevent log.

Broadcast alarms: yes/no user definable, but ifyes, always to Log file.

Standard Device alarms: yes, always to Log file.

description Description of alarm (optional) Broadcast alarms: fixed at “GEMIS defined”

Standard Device alarms: fixed at “GEMIS stddevice alarm”.


System Level Activities Required to Import Signals intothe CIMPLICITY HMI Point Database

This section provides procedures for importing signals into a CIMPLICITY HMIproject Point Database.

À To import signals from a device(s)

The following steps are performed using the GE Control System Toolbox:

1. From the toolbox, use the System Device to define all the Resource IDs thatwill be used in the project. The Resource ID names need to match the ResourceIDs defined in the CIMPLICITY HMI project.

2. Post the System Device to the SDB.

Refer to the manual, GEControl System Toolbox,GEH-6333.

3. Configure the device(s) that will be mapping signals to Ethernet or DLAN+ foruse by the CIMPLICITY HMI project. When the appropriate signals are mappedto Ethernet or DLAN+ within the toolbox, there is a field to indicate whichResource ID is to be associated with the mapped signal. Assign the Resource IDfor each signal as desired.

4. Post the device(s) to the SDB. This stores the signal data for each device in theSDB.

The following steps are performed using the GEMIS Tools for CIMPLICITY:

5. Configure selected devices and Resources in CIMPLICITY HMI project thatcorrespond to the ones being imported. Refer to the table Point/Signal Mappingon page 148.

6. In the SDB Utility, check that the correct project and SDB Server/database ischosen.

7. From the Edit menu, choose Select Resources. A list of AvailableResources (Resource IDs) and Selected Resources is displayed.

8. The Selected Resource IDs determine the signals that are imported into thePoint Database. Edit the list by adding or removing resources and click OK.



10. Choose SDB All to import all signals associated with the chosen Resourcesregardless of which device owns them. Choose the network from which to importsignals.

– Or –

Choose SDB Device and choose one device from the displayed list of devices.Only the signals owned by the device on the Selected Net and in the SelectedResource list are imported.

11. Click OK. The signals are imported to the CIMPLICITY HMI project PointDatabase.

Note Only the devices connected to the selected network that the CIMPLICITYServer is connected to, show in the Resource list.

System Level Activities Required to Import Alarms intothe CIMPLICITY HMI Point Database

This section provides procedures for importing alarms into a CIMPLICITY HMIproject Point Database.

À To define and use Broadcast alarms

Refer to the manual, GEControl System Toolbox,GEH-6333.

The following steps are performed using the GE Control System toolbox:

1. From the toolbox, use the System Device to define all the Broadcast alarmgroups, and their associated alarms. Post the System Device to the SDB.

2. Bind the appropriate UC2000 and then Configure the UC2000(s) to send desiredalarms under appropriate conditions using the _ALARM_XMIT block. The_ALARM_XMIT block is configured using an Alarm Group (Search or Display)and the index for the alarm group..

3. Save, build and download the UC2000.

The following steps are performed using the GEMIS Tools for CIMPLICITY:

4. From the SDB Utility, make sure the correct project and SDB server/Database isselected.

5. From the tools/Import menu, choose Alarms .

6. Choose the options desired and click Import Now .


The Log window displays the progress of the import. If the import is not completelysuccessful, problems can be viewed in the Log file.

À To view the log file

1. From the View menu, choose Clie_Log File.

2. Double-click on the desired log file name.

– Or –

1. From the View menu, choose Utility Log File.

2. Scroll to the end of the file to see the latest activity.

The Log window displays the progress of the import. All information displayed in theLog window is also written to the SDB Utility Log file.

À To generate and view Broadcast alarms

1. The device, if configured properly, will generate Broadcast alarms when theprogrammed conditions occur.

2. In order for the Broadcast Alarms to be received and sent to the CIMPLICITYHMI Alarm manager, the following products from the GEMIS Tools forCIMPLICITY need to be installed:

• Mode Logger

• Message Archiver

• GECAMS (Alarm Manager service)

3. Mode Logger must be running on a PC connected to DLAN+.

4. Use the CIMPLICITY HMI Alarm Viewer to view generated alarms.

Or, use DlanView Tools For CIMPLICITY.


Notes

GEH-6372D GEMIS Tools for CIMPLICITY Glossary of Terms • 165

Glossary of Terms

Alarm Manager InterfaceReceives messages from the Message Archiver through Ethernet.

alarm messageSelected messages that announce a device or process condition.

ARCNETAttached Resource Computer NETwork. A LAN communications protocoldeveloped by Datapoint Corporation. The physical (coax and chip) and datalink(token ring and board interface) layer of a 2.5 MHz communication network whichserves as the basis for DLAN+. See DLAN+.

applicationPrograms that perform specific tasks, unlike system software that maintains andorganizes the PC and utilities. See program.

back-chainA techniques used to substitute source logic for an output signal repeatedly until noother output signal can be found.

boardPrinted wiring board.

BooleanA binary algebra that use the logical operators AND, OR, XOR, and NOT, andwhose outcomes consist of logical values (either TRUE or FALSE).

CIMPLICITY HMICIMPLICITY HMI contains Windows NT applications and services for monitoringand control of industrial equipment. These applications are configured in aserver/viewer architecture. The server collects and distributes the data with thecontrollers. The viewers present the data in various ways and also provide ways tosend data back to the controllers.

configureTo select specific options, either by setting the location of hardware jumpers orloading software parameters into memory.

control messageA specific message from one device to another that directs a device to perform anaction, such as set a value.

166 • Glossary of Terms GEH-6372D GEMIS Tools for CIMPLICITY

deviceAnything that can communicate point data to CIMPLICITY software such as theprogrammable controller Series 90-70 PLC. CIMPLICITY software can read datafrom and write data to devices.

DLAN+GE Motors & Industrial System’s LAN protocol, using an ARCNET controller chipwith modified ARCNET drivers. A communications link between exciters, drives,and controllers, featuring a maximum of 255 drops with transmissions at 2.5 Mbs.

dropA connection point between a communicating device and a communications network.

eventAn action, such a command, that generates a message.

EthernetLAN with a 10 Mbaud collision avoidance/collision detection system used to linkone or more computers together. Basis for TCP/IP and I/O services layers thatconforms to the IEEE 802.3 standard, originally developed by Xerox, Digital, andIntel.

firmwareCategory of memory chips that hold their content without electrical power, such asEEPROM. Firmware becomes hard software when holding program code.

flashA non-volatile programmable memory device.

groupsSee Resources.

hexadecimal (HEX)The base-16 counting system, whose digits are 0 through F. The letters A through Frepresent the decimal numbers 10 through 15. Two hex digits are needed to represent1 byte.

hostComputer that performs centralized functions such as making program or data filesavailable to other computers.

interrupt request (IRQ)A network method in which workstations can pause a server to get service. Theserver resumes its prior operation after handling the station’s request.

messageA structure or set of parameters used for communicating information or a request.Messages can be passed between the operating system and an application, threadswithin an application, and windows within an application.

GEH-6372D GEMIS Tools for CIMPLICITY Glossary of Terms • 167

Message ArchiverReceives messages from Mode Logger through TCP/IP. It then translates the rawmessages into text strings and writes them into the Message database. The files canbe viewed by DlanView.

Message Archiver DatabaseThe Message Archiver Database contains all translated DLAN+ messages and alarmsfrom the Message Archiver. Use DlanView to view the saved file.

monospaceA font, such as Courier New in which the width of each character is the same,producing output that looks like typed characters.

PCLGMode Logger assembly consisting of a motherboard (CCIC), a daughter board(CCIE), PSP6800PCLD boot loader firmware, and a BNC/BNC/DB-25 LAN bypassconnector.

Point DatabaseIn CIMPLICITY, input or output point data associated with signals in the SDB.

programTransforms the PC into a tool for performing a specific kind of work.

projectA configuration of a control system(s), including its related data.

rampTo change gradually over time in equal increments.

registryThe Windows NT registry is a database repository for information about acomputer’s configuration. It is organized in a hierarchical structure, and is comprisedof subtrees and their keys, hives, and value entries.

ResourcesAlso known as groups. Systems, such as devices, machines, or stations where work isperformed, or areas where several tasks are carried out. Resource configuration playsan important role in the CIMPLICITY system by routing alarms to specific users andfiltering the data users receive.

shared memoryMemory accessed by more than one process or thread in a multitasking environment.Processes or threads operate under a set of rules that prevent them from modifyingthe same addresses simultaneously.

168 • Glossary of Terms GEH-6372D GEMIS Tools for CIMPLICITY

Status_SGE proprietary communications protocol that provides a way of commanding andpresenting the necessary control, configuration, and feedback data for a device. Theprotocol over DLAN+ is Status_S. It can send directed, group, or broadcastmessages.

Status_S pagesDevices share data through Status_S pages. They make the addresses of the points onthe pages known to other devices through the system database.

subnetAny lower network, identified by the network ID, that is part of the logical network.Subnets can divide large networks into smaller portions and assign a systemadministrator to each portion.

System Database (SDB)The database where data files that contain signals and I/O points are stored. The SDBallows devices to share signals. (CIMPLICITY Point Database is a subset of signalsin the SDB.)

SDB ServerA program that runs in the background and reads or writes data to the SDB at therequest of the toolbox and other applications.

SDB Server ControlA Windows NT application used to start and stop the SDB Server. It is also used toperform several maintenance function on the SDB Server.

TCP/IPCommunications protocols developed to inter-network dissimilar systems. It is aUNIX standard, but is supported on almost all systems. TCP controls data transferand IP provides the routing for functions such as, file transfer and e-mail.

timestampA value that specifies the time data was created, modified, accessed, or received.

view lineOne line of data in a static or dynamic view of a DlanView.

Problem ReportGeneral Electric Company

Name Telephone Number

Company Name Fax Number

Address Job Site

GE Requisition Number

GEMIS Tools for CIMPLICITY

Description of PC Hardware:Brand Processor Type Processor Speed (MHz)

� 486 � Pentium � OtherDescription of PC SoftwareVersion (see Help, About SDB utility) Windows NT Version Amount of Memory

Problem Description (Describe problem thoroughly. Include sequence leading up to problem. If the program experienced a runtimeerror, attach a printout of the error.log file contained in the tools directory).

Detach, fold, and mail − or fax this side only.

To:GE Industrial Control SystemsProduct Service, Room 1911501 Roanoke Blvd.Salem, VA 24153-6492 USAFax: 001-540-387-8606

.........................................................................Fold here and close with staple or tape .........................................................................

Placestamphere

GE Motors & Industrial SystemsProduct Service, Room 1911501 Roanoke Blvd.Salem, VA 24153-6492 USA

............................................................................................. Fold here first ..............................................................................................

Reader CommentsGeneral Electric Company

We welcome comments and suggestions to make this publication more useful.

Name Telephone Number

Company Name Fax Number

Address Job Site

GE Requisition Number

Publication No. Issue/Revision Date Today’s Date

GENERAL COMMENTS

Excellent Good Fair Poor

Contents � � � �

Organization � � � �

Technical accuracy � � � �

Clarity � � � �

Completeness � � � �

Drawings, figures, and tables� � � �

Referencing and tables ofcontents

� � � �

Readability � � � �

SPECIFIC COMMENTS (Corrections, information that could be expanded, and so on)

Page Number Comment

Other suggestions for improving this publication:

As compared to publications from other manufacturers of similar products, how would you rate this document?

� Superior � Comparable � Inferior � Do not knowIndicate the type of user/reader function that best describes you:

� System Integrator � Distributor � OEM � Installation� Programmer � Maintenance � Operator � Other (please specify)

______________________Detach, fold, and mail − or fax this side only.

To:GE Industrial Control SystemsTechnical Publications, Room 1911501 Roanoke Blvd.Salem, VA 24153–6492 USAFax: 001-540-387-8606

.........................................................................Fold here and close with staple or tape .........................................................................

Placestamphere

GE Motors & Industrial SystemsTechnical Publications, Room 1911501 Roanoke Blvd.Salem, VA 24153–6492 USA

............................................................................................. Fold here first ..............................................................................................

gfk6372d cimplicity configuration tools

Documents

trademark of xerox corporation

d gemis tools

gemis equipmentgeh

important procedure

destruction of equipment

unitedstates of america

windows nt

issue date