Geh 6407 Control System Solutions (Maintenance and Diagnostics Applications)

g
GEH-6407
(Supersedes GEH-6372)
GE Industrial Systems
Control System Solutions

Maintenance and Diagnostics Applications
Publication: GEH-6407
Issued: 1999-11-11
Control System Solutions

1999 General Electric Company, USA.
All rights reserved.
Printed in the United States of America.
These instructions do not purport to cover all details or variations in equipment, nor to provide
every possible contingency to be met during installation, operation, and maintenance. If further
information is desired or if particular problems arise that are not covered sufficiently for the
purchasers purpose, the matter should be referred to GE Industrial Systems, Salem, Virginia,
USA.
This document contains proprietary information of General Electric Company, USA and is
furnished to its customer solely to assist that customer in the installation, testing, operation,
and/or maintenance of the equipment described. This document shall not be reproduced in whole
or in part nor shall its contents be disclosed to any third party without the written approval of GE
Industrial Systems.
ARCNET is a registered trademark of Datapoint Corporation.

Ethernet is a trademark of Xerox Corporation.
IBM is a registered trademark of International Business Machines Corporation.
Intel is a registered trademark of Intel Corporation.
Pentium is a registered trademark of Intel 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.
Safety Symbol Legend
Indicates a procedure or condition that, if not

strictly observed, could result in personal injury or
death.
Indicates a procedure or condition that, if not

strictly observed, could result in damage to or
destruction of equipment.
Indicates a procedure or condition that should be

strictly followed in order to optimize these
applications.
Note Indicates an essential or important procedure, condition, or statement.

To prevent personal injury or equipment damage
! caused by equipment malfunction, only adequately

trained personnel should modify any
programmable machine.
Warning
The example and setup screens in this manual do

! not reflect the actual application configurations. Be
sure to follow the correct setup procedures for
your application.
Caution
Contents
Chapter 1 Overview 1-1

Introduction............................................................................................................................ 1-1
Before Beginning ................................................................................................................... 1-1
How to Use this Manual........................................................................................... 1-1
Conventions ............................................................................................................. 1-3
Chapter 2 Installation 2-1

Introduction............................................................................................................................ 2-1
Computer Requirements......................................................................................................... 2-1
Installing Control System Solutions ....................................................................................... 2-2
License Key ............................................................................................................. 2-3
Destination Directory............................................................................................... 2-3
Registration License Agreement .............................................................................. 2-4
Product Selection ..................................................................................................... 2-5
Uninstall Products.................................................................................................... 2-5
Chapter 3 Mode Logger 3-1

Introduction............................................................................................................................ 3-1
Concepts................................................................................................................................. 3-1
Mode Logger (Modelogr.exe)................................................................................. 3-2
Message Archiver (MsgArchiver.exe) ..................................................................... 3-3
Fault Text Database ................................................................................................. 3-3
Message Archiver Database..................................................................................... 3-3
Configuration ......................................................................................................................... 3-4
Mode Logger Settings.............................................................................................. 3-5
Message Archiver Settings....................................................................................... 3-6
PCLG Assembly..................................................................................................................... 3-7
Settings..................................................................................................................... 3-7
Memory Conflicts and BIOS Problems.................................................................... 3-8
Troubleshooting ..................................................................................................................... 3-9
Chapter 4 Diagnose 4-1

Introduction............................................................................................................................ 4-1
Concepts................................................................................................................................. 4-1
Using Diagnose ...................................................................................................................... 4-3
Menus Commands.................................................................................................... 4-4
Toolbar Commands.................................................................................................. 4-6
Settings..................................................................................................................... 4-7
Configuration ....................................................................................................................... 4-12
Startup.................................................................................................................... 4-12
Command Line Arguments .................................................................................... 4-13
Live Diagnostic...................................................................................................... 4-13
Diagnostics Examples .......................................................................................................... 4-14
Fault Diagnostics ................................................................................................... 4-16
GEH-6407 i
?@ABCD@EFGHIJ@KILLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL MNOP
Q@RBCD@EFGHIJ@KILLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL MNST
!"#$%$&'()*$+!!,-$./01!/# %23

UGJVHWXKJ@HG LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNO
ZHGKB[JILLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNO
\I@GFCD?]^_C`JEJXICaHG@JHV LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNb
\I@GFCaBGXICZHccEGWI LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNM
ZHGd@FXVEJ@HGLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNe
DEJEfEIBC?HKEJ@HGLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNe
D?]^_g LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNe
D@I[REhC`@iB LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNj
`JEJXICkEV LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNj
lVHXfRBImHHJ@GF LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL YNj
!"#$4$."--5"$61"7 423

UGJVHWXKJ@HG LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNO
ZHGKB[JILLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNO
DEJECQRHnLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNS
aBIIEFBCZHRHVI LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNS
\I@GFCaBIIEFBCo@BnLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNb
\I@GFCaBGXICZHccEGWI LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNM
ZHGd@FXVEJ@HGLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNe
DEJEfEIBC?HKEJ@HGI LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNe
D@I[REhC`BJJ@GFI LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNj
p[BVEJ@HG LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNq
rsEc[RBI LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNOS
`@GFRBCZHRXcGC`BEVKmLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNOb
aXRJ@[RBCZHRXcGC`BEVKm LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNOM
t@RWKEVWC`BEVKmBI LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL eNOj
89/--#:$/;$<"#=-
>0?"@
## $%&'()*+
Chapter 1 Overview
Introduction
Windows 95 is currently not This manual describes applications used in GE Industrial Systems control systems.
supported. The applications are a set of Windows NT software applications, which run on an
IBM PC compatible personal computer (PC). Refer to the specific application
listed in the next section.
To prevent personal injury or equipment damage caused by

equipment malfunction, only adequately trained personnel
should modify any programmable machine.
Before Beginning
Windows-based screen This manual describes each feature of the applications. It presumes that the user has
borders may vary in already installed Windows NT. This manual also assumes that the user possesses at
appearance. least a medium-level knowledge of Windows. Hardware requirements and
instructions for installing applications are in Chapter 2.
How to Use this Manual

This manual is organized as follows:
Chapter 1 Overview Provides a functional overview of the different applications.
Chapter 2 Installation Describes the hardware required to operate the
applications. It also provides procedures for installing the software into the PC and
connecting the PC to the control system.
Chapter 3 Mode Logger Provides procedures for using the Mode Logger
application to capture messages on the drive local area network (DLAN+).
Chapter 4 Diagnostics Provides procedures for using the Diagnose application,
which translates fault diagnostic messages from Message View.
Chapter 5 DLAN+ Status Monitor Provides procedures for using the Status
Monitor to view the status of the drops on a particular DLAN+.
GEH-6407 Maintenance and Diagnostics Applications Chapter 1 Overview 1-1

Chapter 6 Message View Provides procedures for using the Message View
application to view the status of drops on a particular DLAN+.
Appendix A SDB Browser Used to view the contents of an SDB database,
display the topology of a system, perform a filtered signal search on the SDB, list
system scales, and more.
Glossary Provides definitions of configuration terms and tool concepts.
Refer to the Table of Contents for the organization of these chapters.
1-2 Chapter 1 Overview GEH-6407 Maintenance and Diagnostics Applications

Conventions
The following conventional terms, text formats, and symbols are used throughout
this documentation for the described applications.
Note Other documents may use different conventions.
Convention Meaning
Bold Indicates that the word is being defined.
Arial Bold Indicates the actual command or option that is chosen from a
menu 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. For
example, the display should now read SDB has stopped. Italic
also emphasizes new terms, margin notes, and the titles of
figures, chapters, and other books in the toolbox package.
UPPERCASE Indicates a directory, filename, or block name. Lowercase letters
can be used when typing names in a dialog box or at the
command prompt, unless otherwise indicated for a specific
application or utility.
Courier Represents examples of screen text or words and characters
New that are typed in a text box or at the command prompt.
Indicates a procedure.
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 command
name. Then press the Enter key to choose the menu command. The menu can also
be 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 that
asks the user to supply more information.
If a command turns a feature on and off, a checkmark ( ) appears by the command
name when the feature is on.
When a command ends with an arrow ( ), the menu cascades to display more
command names.
If a command name is grayed out, it indicates that the command does not apply to
the current situation or there is another selection or action before choosing the
command.
Related Publications
GE provides system instruction manuals that include publications for the different
components of each product. Contact your nearest GE sales office or authorized GE
sales representative if you need additional manuals or have questions about the
publications.
GEH-6407 Maintenance and Diagnostics Applications Chapter 1 Overview 1-3

Chapter 2 Installation
Introduction
Section Page
Computer Requirements .......................................................................................... 2-2

Installing Control System Solutions ........................................................................ 2-2
This chapter describes the PC and installation requirements for the products in
Control System Solutions. Each product is defined with specific requirements and
any additional system dependencies. These products include the following:
System Integration Control System Toolbox
Applications includes SDB
Utility, SDB Exchange, System Integration Applications
DLAN+, GECAMS, ICN, Innovation Series Controller*
Data Historian and more.
Innovation Series Drive*
Maintenance & Diagnostics AC/DC/EX2000 Drive*
includes Mode Logger, Message
Archiver, Message Viewer,
Diagnose, DLAN+ Status, and Trend Recorder Data Historian* (requires SDB)
more.
SDB Server
Toolbox dependent applications are denoted with an *.
GEH-6407 Maintenance and Diagnostics Applications Chapter 2 Installation 2-1

Computer Requirements
The minimum PC requirements are determined by the selected product combination
and the topology configuration of the PC(s). The minimum requirements to use the
Control System Solutions products are as follows:
A cursor-positioning device is
highly recommended. 100 MHz processor (Pentium 166 or higher recommended)
Microsoft Windows 95 or Windows NT 4.0
VGA display (640 x 480 x 16 color or gray scale)
16 MB RAM in Windows 95 (32 MB recommended)
Or 24 MB RAM in Windows NT (32 MB recommended)
Serial port for direct connection to a controller or drive
PCA198 (ARCNET) board (required if GE DLAN+ Devcom or DLAN+ Driver
is installed )
Printer (with appropriate Windows driver installed)
Installing Control System Solutions

For assistance, contact: Control System Solutions installs various products for control systems as selected in
the setup program. It is recommended that you exit all Windows programs before
Industrial Systems
beginning. A dialog box will prompt you for a license key, which can be found on
General Electric Company
the actual CD. Also, you must agree to the standard Software License Agreement for
Product Service Engineering
these products.
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA A default destination directory is set for all products selected. This directory can be
Phone + 1 540 387 7595 modified, but only during the first installation. Setup installs the required
Fax + 1 540 387 8606 components and checks available disk space before copying files. You can also
(replace + with the choose to cancel setup and exit at any time before you initiate the selected products.
international access code)
To install from a CD
Install the desired products 1. Place the Control System Solutions CD in the disk drive.
from CD, following the
2. The Setup program executes automatically.
directions on the screen.
Then, install each product file 3. Follow the Setup instructions from the screen.
starting with the SDB
product.
2-2 Chapter 2 Installation GEH-6407 Maintenance and Diagnostics Applications

License Key
Enter the License Key number.

This number is printed on the
actual CD. The number is not
case sensitive.
Destination Directory
The destination directory for

each product is set to the
default directory C:\Program
Files\GE Control System
Solutions. If desired select a
different directory to load the
products.
This dialog box option can

only be selected during the
initial installation of these
products. After that all future
installs and upgrades default
to the first directory selected.
Select a directory and click Next. Setup automatically continues to load. The Control
System Solutions product selection dialog box displays to allow you to select desired
products described in the following sections.

Registration License Agreement
The following License Agreement dialog box displays during installation. The
license must be read and agreed to before installation can continue.
Please read the entire

agreement (scroll bar must
be at the bottom of the
dialog box).
Click Yes to accept the

agreement.

Product Selection
Note A description of each product and the disk space required displays when the
product is selected. For additonal information on a product, refer to the
documentation noted in the description.
You must click to the left of each

product you want to install. A
check mark must display beside
the product name.
Click the product name in the left

column to check all the
application in that group. Click
again to uncheck all.
The number beside each product

indicates the amount of space
required for that product.
A description of each product

displays when it is selected
(highlighted).
Products that were not purchased as part

of the Control System Solutions CD do not
appear in the product selection list.
Uninstall Products
Note Before upgrading to Release 5, product components should be uninstalled and
then installed again using the Release 5 CD or network installation.
To uninstall product(s)
1. Click Windows Start button, Settings and click Control Panel.

2. From the Control Panel dialog box, double-click on Add/Remove
Programs. The Add/Remove Program Properties dialog box displays.
3. Click on the tab Install/Uninstall. A list of all installed programs displays.
4. From the list box, click on the program(s) to uninstall.
Or
To remove all products, click GE Control System Solutions Uninstaller.
5. Click Add/Remove.

The following screen displays to show when uninstall is complete and the status of
all items deleted.
If you choose to remove all products by selecting

GE Control System Solutions Uninstaller, the
following dialog box displays. All installed
products are listed and will be removed.

Chapter 3 Mode Logger
Introduction
Section Page
Concepts .................................................................................................................. 3-1

Configuration ........................................................................................................... 3-4
PCLG Assembly ...................................................................................................... 3-7
Troubleshooting ....................................................................................................... 3-9
This chapter describes the Mode Logger system. The Mode Logger and Message
Archiver Services read and save messages transmitted on DLAN+. These messages
can be viewed with Message View (see Chapter 6). The Mode Logger Control
application manages the Mode Logger and Message Archive Services. It is installed
as part of the Mode Logger and Message Archiver Services.
Concepts
Mode Logger and Message The Mode Logger service reads raw messages on the DLAN+ and sends them to the
Archiver are implemented as Message Archiver. The Message Archiver translates the messages, using information
Windows NT services. They read from the System Database (SDB), and writes the messages to the Message
are started and stopped by the Archiver Database.
Windows NT Service
GECAMS provides a connection to the CIMPLICITY HMI Alarm Manager
Manager. The user controls
Runtime Process (AMRP) from the Message Archiver. Using this interface, the
the services indirectly with
Message Archiver can send DLAN+ alarm messages to CIMPLICITY, where they
the Mode Logger Control
can be viewed with the CIMPLICITY HMI Alarm Viewer (AMV) and optionally
application, which writes
logged into the CIMPLICITY HMI Alarm/Event Database.
configuration data into the
Windows NT registry and Message View can display the DLAN+ messages recorded in the Message Archiver
sends commands to the Database. The Fault Text Database contains the text messages corresponding to the
Windows NT Service fault codes and device types transmitted on DLAN+.
Manager.
GEH-6407 Maintenance and Diagnostics Applications Chapter 3 Mode Logger 3-1

The following diagram displays the data flow in the Mode Logger system.
* Selected message types Control Messages

CIMPLICITY HMI Project
Signal Names in
DLAN+ Message
Message
Alarm Manager
Interface Message Archiver Archiver
(GECAMS) Database
Control
Messages
SDB
CIMPLICITY Alarm API
CIMPLICITY ICN Messages

Alarm Mgr from Ethernet
(AMRP)
Message View
Mode Logger PC 1 Mode Logger PC 2
AlarmView
PCLG Assembly PCLG Assembly Optionally over Ethernet
CIMPLICITY
Alarm/Event Within a single PC
Database DLAN+ Network A DLAN+ Network B
* Device faults and process alarms

transmitted by DLAN+ devices
The proper display of messages from different

DLAN+s depends on the two Mode Logger PCs
having the same time. If the two PCs differ
significantly, messages from one DLAN+ always
appear at the top of the display, since they are
sorted by time. If the time difference is large
enough, the entire display may consist of messages
from one DLAN+, giving the impression that no
messages at all are being sent on the other DLAN+.
For more information, refer to manual GEH-6406,
Chapter 9, Network Time Protocol.
Mode Logger (Modelogr.exe)

To install Mode Logger, The Mode Logger service must be installed and run on the same PC as the
choose it from the product list DS6815PCLG Mode Logger assembly (PCLG). Runtime parameters for the PCLG
during installation (see assembly and Mode Logger are stored in the Windows NT registry. When executed,
Chapter 2). 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 valid
signature in the shared memory.
Downloads the firmware into the PCLG and sends the start command.
Periodically checks the shared memory for incoming messages, reads messages
into a buffer, and sends them to the Message Archiver.
3-2 Chapter 3 Mode Logger GEH-6407 Maintenance and Diagnostics Applications

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

The Fault Text Database provides information for a specific fault code and device
type. It is used by Message Archiver at runtime to translate fault codes into the
correct 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)
Innovation Series Controller
Series 90-70 Programmable Logic Controller (PLC)
Note If a device is updated independently on a process or customer site, new fault

text messages will not be available to the Message Archiver. You must update Mode
Logger to the most recent release.
Message Archiver Database

The Message Archiver Database contains all translated DLAN+ messages and
alarms from the Message Archiver. The database is updated periodically. Copy the
file to a new location to save a database for later analysis. Use Message View to
view the saved file.

Configuration
The Mode Logger System Control is used to set up the Mode Logger and
Message Archiver services.
To start the Mode Logger Control application
Select the GE Control Systems Solutions program group/folder and click
Mode Logger Control .
The Mode Logger System Control window is displayed.
The Mode Logger System Control window allows the user to start and stop the two
programs that make up the Mode Logger system. The programs are:
Mode Logger (PCLG assembly)
Message Archiver
If one or both programs are not installed, the program(s) status in the Mode Logger
System Control window under Currently will be Not Installed. Not Installed
means that you will be unable to configure or start that program. After installing the
program and running the initial setup, you can start the programs automatically when
Windows NT first starts up by doing the following:
To set up the Mode Logger or Message Archiver for startup
1. From the Mode Logger System Control window (shown above), click
Settings.
The Mode Logger Settings dialog box is displayed. It contains a tab for the Mode
Logger and the Message Archiver program.
2. Choose a startup mode for each program (Automatic, Manual, or Disabled).

Mode Logger Settings
The Mode Logger tab is set as follows:
DLAN+ Net Number identifies the DLAN+

that the PCLG is connected to as defined in
the SDB. The default is one.
Process rate is the rate the host program

empties the DLAN+ message buffers in
the shared memory of the PCLG
assembly. If the number is too small, the
host program uses excessive CPU time
checking these buffers unnecessarily. If
the number is too large, the buffer can fill
and overflow before the host program can
check and data will be lost. The default
rate is 250.
Message Archiver Location is the PC that

hosts the Message Archiver program.
Mode Logger messages are sent to the
Message Archiver either on This PC (local
host) or Remote PC (through TCP/IP).
Startup Mode controls how the Mode

Logger program is started. In most cases,
it should be set to Automatic.

Message Archiver Settings
The Message Archive tab is set as follows:
Limit size of message database allows the user

to enter a maximum number of records. Once
the maximum number of records is reached,
the oldest records are overwritten by newer
messages. The limit depends on the size of the
hard drive and the requirements of other
programs. Allow a larger message database
for troubleshooting a system problem.
SDB Location is the Server Name and Path

directory for the SDB. If the SDB is on the
same PC as Message Archiver, enter
localhost. The Message Archiver uses the SDB
to translate the device IDs, drop numbers,
word offsets, and such into device and 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 a different PC, set the
startup mode to Manual or Disabled to avoid
unnecessary use of system resources.
If the CIMPLICITY HMI Alarm Manager is available in the system, check the box
Send GE DLAN+ alarm messages to CIMPLICITY Alarm Manager. The
following field displays under Interface to CIMPLICITY.
Refer to GEH-6306 Chapter

7, section, Alarm Manager CIMPLICITY Server node identifies the server PC. The Alarm Manager Interface
Service. program must run on the CIMPLICITY Server. If the current PC is not the
CIMPLICITY Server, choose Remote PC option button and enter the name of the
PC that is the CIMPLICITY Server node.

PCLG Assembly
Mode Logger communicates Mode Logger program reads raw DLAN+ messages through the DS6815PCLG
with the SDB Server, Message Mode Logger board (PCLG) assembly and sends them to the Message Archiver
Archiver and CIMPLICITY program. The Message Archiver decodes these messages using data from the SDB
HMI Alarm Manager using and stores the resulting text messages in the Message Archiver Database. If
TCP/IP. CIMPLICITY HMI is available, the device fault and other alarms received on the
DLAN+ can also be sent to the CIMPLICITY HMI Alarm Manager for display and
storage. Message View reads, sorts, and displays the messages from the Message
See section Data Flow. Archiver Database.
Settings
The PCLG assembly holds the daughter board DS6800CCIE (CCIE).
OPEN
CCIE DAUGHTER BOARD
87654321
LEDs
SW 1
J6 J5
J3 J4 J7
Setting the PCLG Assembly

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

0xD0000
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 indicates 2. Install the PCLG in the PC and connect the DLAN+ cable. Leave the top of the
activity on the network. PC open so the light-emitting diodes (LEDs) are visible.
3. Start the PC. The yellow LED should begin to blink steadily (about twice per
second). A non-blinking LED is bad. If the LED does blink, then install the
Mode Logger programs.
4. Check the settings for Mode Logger (see Chapter 3) and start it. The yellow
LED on the PCLG may be solid at first. Then it may flash twice per second. The
light should eventually flicker intermittently.

If the LED(s) are out and the cable is connected, check for one of the following:
Bad PCLG
DLAN+ cable not connected to a valid DLAN+
Problem with BIOS
Memory Conflicts and BIOS Problems

The PCLG communicates with the PC host through shared RAM. Anything that
interferes with this memory can cause problems. In particular, if a device such as an
SCSI adapter or a network card is configured to 0xD0000, or 0xD8000 or any
address 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 to
the shared memory on the PCLG assembly. MapMem attempts to map a section of
the PC's memory to the PCLG memory. If another device has already mapped this
memory, MapMem fails and Mode Logger does not run.
To check for conflicts
1. From Windows NT (Version 4.0), choose Programs and then choose
Administrative Tools.
2. Choose Windows NT Diagnostics and the tab Resources.
3. Click
.
If Mode Logger is installed, the following line displays:
000D0000 - 000DFFFF MapMem 0 Isa
If any part of the address range is mapped by another device, MapMem will not start
and Mode Logger will not run. If the competing device cannot be configured to use
another memory location, then either that device or the PCLG must be moved to
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 to
communicate with the PCLG assembly.
Revision should be 4.05.1.1a
with 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 the
TMI website http://www.texmicro.com.
Mode Logger errors are written to the Windows NT Event Log.

To view error messages
Messages indicating that the 1. Click on Windows Start, Programs, and Administrative Tools
PCLG is active and capturing (Common).
messages probably mean that
there is no BIOS problem or 2. Click the Event Viewer icon.
memory conflict. 3. Choose the Log menu and Application.
4. Search for Mode Logger messages.
Note If a bad signature 0xFFFF reported, it is probably a bad PCLG. Other invalid
signatures are probably 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 Message View set up
Check the Windows NT Event Log for errors (event.dbf file), which is
accessed through Programs/Administrative Tools/Event Viewer.
Command message(s) have The signal name cannot be found in the SDB. Check the Windows NT
net1\drop140\word1\bit0 instead of the Event Log to make sure there was no problem initializing from the SDB.
signal name Signals may need to be posted or reposted.
Receiving messages from one network but Check that both PCLGs and both Mode Logger programs are running and
not the other (with two DLAN+s and two sending messages to the correct MsgArchiver.
Mode Logger assemblies)
Check that the system time on both Mode Logger PCs is the same. The
PCLG time is initially set by the host PC. If one PCs time is slow, all its
messages appear at the bottom of the list, or not at all if there are a lot of
messages. To verify that each Mode Logger is sending messages
correctly, set up a separate MsgArchiver for each Mode Logger. Send
each Mode Logger's message to its own MsgArchiver. Then, when both
have been verified separately, send all messages to the same
MsgArchiver.
Check the CIMPLICITY HMI status log on the CIMPLICITY server. (From
Device faults appear in Message View, but the CIMPLICITY HMI project, choose the Tools menu, and choose Status
not in the CIMPLICITY HMI Alarm Viewer Log). Messages may indicate that alarm IDs are not configured or that a
resource is missing. Required alarms must be configured for each device
using the CIMPLCITY HMI alarm configuration application. If a resource is
missing, enter it manually, using the Resources icon in the CIMPLICITY
HMI project.
If there are no errors in the Status Log, there could be a problem in the
transfer of messages from MsgArchiver to the CIMPLICITY HMI Alarm
Manager. Check all the settings in the Mode Logger Configuration
Program. Check that the CIMPLICITY server host name is correct.
Check the TCP/IP connection to the CIMPLICITY server. From the DOS
prompt type ping <hostname>. On the CIMPLICITY server, make sure
the GECAMS box is checked under Project/Settings, and make sure it
runs when the CIMPLICITY project is started. Use the Windows NT Event
Viewer to check the application log for any error indications on both the
Message Archiver PC and the CIMPLICITY server PC.

Chapter 4 Diagnose
Introduction
Section Page
Concepts .................................................................................................................. 4-1

Using Diagnose........................................................................................................ 4-3
Configuration ......................................................................................................... 4-12
Diagnostics Examples............................................................................................ 4-14
This chapter describes the Diagnose application, which translates permissive fault
diagnostic messages from Message View and CimView applications. In the system, a
controller broadcasts a fault diagnostic message on the DLAN+. The Mode Logger
receives the message and stores it in the Message Archiver Database with the time it
was received. This message can be translated by Message View. Live messages are
translated by CimView.
Concepts
Diagnostic messages are processed by Message View (message) or CimView (live).
Message View
Before the Diagnose In Message View, selected parts of the diagnostic message are displayed in
application can be used, it the color cyan. The user double-clicks on this message to initiate the Diagnostic
must be configured with the application and identify the diagnostic message.
location of the Message
Archiver Database. Refer to Diagnose retrieves the message from the Message Archiver Database and
the tab System/Message sends it back to the originating controller.
Archiver Database in the The controller translates the diagnostic message and sends a response back to
Settings menu. the Diagnose application. It displays in the Diagnostic window as a relay
ladder diagram (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 and to
retrieve additional information about the controller.
GEH-6407 Maintenance and Diagnostics Applications Chapter 4 Diagnose 4-1

The Diagnose application sends the request to the controller. The controller
responds with a snapshot of the diagnosed signals current state, and optionally
with a back-chained set of contacts.
Diagnose displays the results on screen. The contacts drawn represent only
those signals that are not in the proper state to allow the requested signal to be
true. It is not the total control logic.
The following figure shows the data flow in the system using both Message View
and CimView:
CimView
Low Pressure Hydraulic Power System
1 2 3
CimView
Boolean Signal
Message View
Status signal Permissive

Diagnostics
Message View
Diagnostic message selected

Signal Details
Innovation Series Controller
Genius
SDB
CPU
BENG
DLAN+
PENG
PCLG
Status Assembly
Status
Signal for Message
Message
Archiver
Database
All Messages All Messages
Mode Logger Message Archiver

Ethernet
Optionally over Ethernet
Within a single PC Diagnostic request
4-2 Chapter 4 Diagnose GEH-6407 Maintenance and Diagnostics Applications

Using Diagnose
Diagnose can display data in four modes. The mode currently being used displays in
the Status bar. The modes are:
FAULTED, which displays when the user chooses (double-clicks) a diagnostic
message displayed in Message View fault diagnostics from the controller
displays as an RLD.
LIVE data, which allows the user to backtrack 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 created from the File menu command, New.
Status Bar Display Source of Diagnostic
FAULTED Message View (blue diagnostic message)
LIVE
Click Live Diagnostic Request or CimView
FILE Disk file
NEW DOC
Click or from File menu, choose New
RLD Logic and Signal Details The Diagnose window has two views to display the fault diagnostic. The left view
view settings can be edited in displays the RLD Logic for the chosen fault diagnostic. The right view displays the
the Options menu. Signal Details for the contact or coil currently highlighted in the RLD Logic view.
The window title/block name is the name of the block. It is displayed with a period
character (.) instead of a backslash (\). For example, func1\out2 is the name of the
block and FUNC1.OUT2 is the name in the window title. The period allows the
diagram 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 perform different
commands. These commands are described in the following sections.
From the RLD Logic view (left side), click on a contact or coil. Its signal data is
displayed in the Signal Details view (right side). Double-click on the contact or coil
to display additional data. The Signal Details data can include the signal name and its
state, description, and fault type. It can also include the time the diagnostic data was
displayed and other data.
Window Title/Block Name
Menu Bar
Toolbar
RLD Logic (diagnostic

data from controller).
Double-click on the
contact to get additional
data. Click on the coil
for the block type, fault
type, and the time of
data display.
Status Bar Active View Mode Fault Diagnostic Signal Details

Menus Commands
File Menu
The File menu allows the user to perform file operations with the commands 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 the options
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.
Exit closes the diagnose

application
Recent File lists and opens the last
four previously opened files.
View Menu
The View menu allows the user to display or not display the Toolbar and 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 allows the user to manage the options required for proper
operation. It also contains settings to manage the on-screen appearance of the
diagnostics data.
Settings allows the user to set options that
determine the amount and appearance of data
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 and
displays the last diagnostic that displayed on
screen. This diagnostic replaces the currently
displayed diagnostic.
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 Settings menu. Or double-
click on the contact or coil.
Signal Memo displays the note

information from the SDB for the currently
selected signal contact or coil in the RLD view.
Live Diagnostics allows the user to enter

data to request a live diagnostic. This displays
the current state of the signal (coil) and why
the signal is in this state.
Change Detect is active when a

diagnostic is received from a PENG-D block.
The default is to display all signals that have
changed state that resulted in a loss of power
since the last scan of the controller. Choosing
this menu item results in a complete diagnostic
independent of changes per scan.
Window and Help Menus

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

Toolbar Commands
The Diagnose application has the following shortcut toolbar commands, which can
be 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 current printer
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 highlighted
signal in the RLD view.
Toggle Signal/Label displays (either the signal name or an internally

generated label) above the contact. A larger percentage of the diagram
can be viewed when the label is displayed.
Increase the size of the contents in the selected view (either RLD or
Signal Details view). The text point size is increased by two points.
Decrease the size of the contents in the selected view (either RLD or
Signal 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 current

state of the signal (coil) and why the signal is in this state.
Perform a complete diagnostic separate from changes per scan. Change

Detect is active when a diagnostic is received from a PENG-D block. The
default displays all signals that have changed state and resulted in a loss
of power since the last scan of the controller.
Obtain context sensitive Help on the selected item. Click and then
click on the item you want help with.

Settings
The Options menu contains five tabs that define display and window settings:
Note The tab SDB/Message Archiver Database must be entered before the
Diagnose application can be used with Message View.
Signal Details selects the items to be Print Options sets the items that are Screen Display Options sets the size
displayed in the Signal Details window, printed and the desired fonts. and position of the screen window,
such as the network name, I/O device which include the RLD Logic Display
type, and device location. (left side) and Signal Details (right)
Relay Ladder Diagram Options defines SDB/Message Archiver Database sets

the settings for the RLD Logic Display, the location of the SDB and Message
such as the text display and grid. Archiver Database.

Relay Ladder Diagram Options
The Relay Ladder Diagram Options tab defines how the RLD Logic Display is
displayed on the screen.
Relay Ladder Diagram Text Display

defines how the contacts are displayed.
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 large displayed on the screen for
large diagrams.
Use Signal Name is the default setting. It

displays the logical signal name over the
contact.
Display Grid displays a grid pattern on

the screen that separates each contact
for viewing.
Display Default Signal Prefix enables

the prefix portion ( }00000\}00001\B20 )
forsignals that are automatically
generated by the controller. Using the
finder, the default signal prefix might be
used to find a signal in the toolbox.
Set Display Text Font defines the font for

the text that displays above the contact.

SDB/Message Archiver Database
The SDB/Message Archiver Database tab allows the user to set the path for the
database(s).
System Database sets the Server

Name and Path to the System
Database. If the SDB is on the same
PC as the Diagnose application,
localhost can be used as the server
name. The path is relative to the
server name.
Message Archiver Database sets the

path to the Message Archiver
Database. Message Archiver
Database is defaulted if the Message
Archiver is installed on this PC.

Signal Details
The selected font also applies The Signal Details tab defines the particular information for each signal that is
to the printing of the signal displayed in the Signal Detail window.
information.
Note To select a detail, click on the box. A check displays in the box . To remove
a detail, click on the 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 the desired signal.
Descriptions allows the user to define

which group of descriptions will display
for the desired signal.
Signal Description Language sets the

language for descriptions to be
displayed in
Clear All Selections cancels all items set Set All Selections sets all items in this Set Signal Display Font defines the font
in this tab. The Language code is not tab. The Language code is not to display the signal details on the
changed. changed. screen.

Print Options
The Print Options tab defines what is printed and the font settings for both the
RLD display and Signal Details.
Note The tab Signal Details defines particular information of the signals.
Signal Details Options prints all of

the signal information that is chosen
in the Signal Details tab
Relay Ladder Diagram Options prints

the RLD to the default printer.
Set Signal Text Font defines the font

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

the text above the contact
To preview the printed diagram, choose

the File menu and the Print Preview
command.

Screen Display Options
The Screen Display Options tab defines how the application window is
positioned on the screen. It allows the Diagnostic window to be maximized on
startup.
Maximize Document Window on

Startup enlarges the Diagnose
window to the full size of the screen
within the application.
Default indicates that the application

position and size at startup will be the
default.
Maximize enlarges the diagnose

window to the full size of the screen.
Specify allows the user to customize

the location of the application on
screen along with the applications
width and height. The maximum
height and width allowed is controlled
by the screen resolution setting.
Configuration
Startup
CimView requests do not use Before the Diagnose application can be used, it must be configured with the location
this database. of the Message Archiver Database. The database path must be assigned before the
first diagnostic request is sent to the application from Message View. See the section
Settings, System/Message Archiver Database for more information.

Command Line Arguments
The command line arguments The diagnose application accepts the command line:
must be used in the CimView
DIAGNOSE /SIG signal name [ device name]
command procedure.
where:
/SIG is required
signal name is a valid point ID that equates to a Boolean signal from a controller
device. Signal name is required. The format of the signal must use the internal
controller form module\signal and the signal must be posted to the SDB.
device name is the device that owns the signal (usually a controller) that has been
entered in the SDB.
Note The bracket characters [ ] are not part of the device name. They imply that
the 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 diagnostics
fault 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 and
Execute.
5. Enter the executable filename and the command line arguments.
Live Diagnostic
Live fault diagnostics can be requested for a signal. The request will return the
current 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 Diagnostic
dialog box displays.

2. Enter the required information as follows:
Signal Name is the signal to be back-chained. This should be a Boolean signal in
the controller (output of a BENG-D or PENG-D block). Enter a name in the standard
controller format (module\signal) or choose from the drop-down list, which contains
all of 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 controller device that owns the signal.
Continuous back-chains the signal regularly every few seconds. If this option is
not checked, 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 Controller 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 Examples
The examples in this section describe the three diagnostic modes, FAULTED, LIVE
and FILE for a task running in the controller. The following screen displays the
Device window of the controller. The name of the controller device is docuc. It has
one task, named task1.
Controller
Task
Blocks

There are three BENG_D blocks with TRUE outputs connected as follows:
To obtain diagnostics and back-chaining, the REQDIAG (Request Diagnostics) input

must transition from a 0 to a 1 and is TRUE, and both DDIAG (Disable Diagnostics)
and DDIAGBD (Disable Diagnostic Back-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 the These three BENG-D blocks solve the following logic:
diagram are Boolean signals.
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 of
the controller as follows:
Fault Diagnostics
Diagnostic messages are displayed in Message View in the color cyan. Double-click
on a diagnostic message to invoke the Diagnose application. The fault diagnostic
data displays as a relay ladder diagram (RLD).
This RLD is not the exact Control logic used in the controller, but is a representation
of the minterm and presents the signals that caused the fault to occur. The following
example shows how this diagram should be interpreted for FAULTED diagnostics.
In the following RLDs, the states of the signals (TRUE/FALSE) are the actual values
when output went FALSE and generated a diagnostic message. For example, in
Example 2 below, bool3 is TRUE and bool1 is FALSE even though the logic only
requires 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. The
RLD 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 RLD
obtained 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 Diagnostics
The examples for Live Diagnostics are identical to the FAULT diagnostics, except in
the Status Bar the MODE displays LIVE instead of FAULTED. If the status of the
coil (TRUE/FALSE) is not available, a Don't Know state displays on the coil.
Example of Live Diagnostics

The following is an example with unknown coil status for LIVE diagnostic.

File Diagnostics
Diagnostic data previously saved in a file can be either in the FAULTED or LIVE
mode. The following example displays the data in the file, FUNC1.STATUS3.dia.
.dia file
active view mode mode
The Status bar indicates that the diagnostic is a FILE mode. The Device
window/signal name, FUNC1.OUR3.dia indicates that this data was obtained from a
*.dia file.

Chapter 5 DLAN+ Status Monitor
Introduction
Section Page
Concepts .................................................................................................................. 5-1

Using DLAN+ Status Monitor................................................................................. 5-3
Configuration ........................................................................................................... 5-6
Troubleshooting ....................................................................................................... 5-7
This chapter describes the DLAN+ Status Monitor application, which is used to view
the status of drops on a particular DLAN+. DLAN+ traffic can also be displayed on a
per drop basis. The DLAN+ Status Monitor can display the drop status as a function
of devices defined in the SDB.
Concepts
This application provides a graphical display of the drop data that the Message
Archiver Service writes to the Message Archiver Database. The DLAN+ Status
Monitor can access any Message Archiver database that is either local to the PC or
exists in a directory mapped to the local machine.
GEH-6407 Maintenance and Diagnostics Applications Chapter 5 DLAN+ Status Monitor 5-1
The following diagram shows the data flow in the system:
DLAN+ Messages
DLAN+
Message Message Messages
Archiver Archiver
Database
Signal Names in
DLAN+ Message
SDB
DLAN+
Status
Mode Mode
Logger Logger
PC 1 PC 2
Optionally over Ethernet
Within a single PC
PCLG Assembly PCLG Assembly
DLAN+ Network A DLAN+ Network B

transmitted by DLAN+ devices
5-2 Chapter 5 DLAN+ Status Monitor GEH-6407 Maintenance and Diagnostics Applications
Broadcast and directed The Message Archiver periodically writes the drop link presence status, the
message counts are written in broadcast message count, and the directed message count for each drop on the
bytes. DLAN+ to the Message Archiver Database. The DLAN+ Status Monitor reads the
data, calculates the appropriate data rates for each drop, and updates the display.
Timestamp is a value that
Timestamp data, which is located in the Message Archiver Database, determines if
specifies the time data was
the data is being actively updated (Live).
created, modified, accessed,
or received.
The drop link presence status can be displayed against the device definitions in the
SDB. The SDB location is read from the Message Archiver Database and the system
topology is read from the SDB by the DLAN+ Status Monitor application. The
following table defines the status of the displayed drop by the background color:
Drop Status Background Color
Defined active drops Green
Undefined active drops Yellow
Defined Inactive drops Red
Inactive drop Black
No current data (not updated by the Message Gray
Archiver for at least two data samples)
Note The SDB location cannot be set by the user. The SDB server name and path
are read from the Message Archiver Database to make sure that the Message
Archiver and DLAN+ Status Monitor application are using data from the same SDB.
Grayed out data indicates that

Mode Logger is not running Or
Message Archiver is either not running or not sending messages to the database
being accessed by DLAN+ Status Monitor Or
DLAN+ is unresolved
DLAN+ Status Monitor can be used without access to an SDB. All functions are
available except the Database Drop Status mode, which reports all live drops as
undefined. Message Archiver will populate the DLAN+ tables even if the SDB
connection cannot be made; however, the DLAN+ name will not be correct.
Using DLAN+ Status Monitor

DLAN+ Status Monitor can display data for any DLAN+, provided the location of
the Message Archiver Database is known and the Mode Logger is either local to the
PC or is mapped to it. The following sections describe the menu commands and
toolbar shortcuts used to configure the application.
GEH-6407 Maintenance and Diagnostics Chapter 5 DLAN+ Status Monitor 5-3

Using Menus Commands
Refer to the section on
Configuration. Settings Menu
The Settings menu has the following commands.
Database allows the user to choose the path of the
Message Archiver database.
DLAN+ allows the user to choose which DLAN+ to

display from Message Archiver 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.
Toolbar Commands
Click To display
Database Drop Status, the link presence status of each drop in relation to the
devices defined in the SDB.
Drop Status, the link presence status of each drop on the chosen DLAN+.
Drop Total Rate, the combined broadcast and directed data rates for each
drop on the DLAN+.
Drop Broadcast Rate, the rate of broadcast messages for each drop on the
DLAN+.
Drop Directed Rate, the rate of directed messages for each drop on the
DLAN+.
Drop Total Count, the combined broadcast and directed message count for
each drop.
Drop Broadcast Count, the broadcast message count for each drop on the
DLAN+.
Drop Directed Count, the directed message count for each drop on the
DLAN+.

Configuration
The 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 Archiver
Database 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 Database
table
1. From the Settings menu, choose DLAN+... The Available DLAN+s dialog
box displays.
2. Choose a DLAN+ from the list box and click OK.
Display Size
The Display Size command can maximize or minimize the screen size used by the
DLAN+ Status Monitor window.
To edit the Display Size
1. From the Settings menu, choose Display Size. The Display Size dialog
box displays:
2. Click the option button for the desired size of the screen display and click OK.
Status Bar
The 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
The DLAN+ Status Monitor displays the DLAN+ data that is periodically written to
the Message Archiver Database by the Message Archiver service. It must also
compare that data with topology information read from the SDB when Database
Drop Status mode is active. Therefore, it is necessary to make the correct connection
to the Message Archiver Database and the SDB.
Mode Logger Control manages the Mode Logger and Message Archiver services. It
Mode Logger Control can resolve issues where the DLAN+ Status Monitor cannot connect to the Message
manages the starting and Archiver Database or is not displaying Live data. Use the Settings menu to determine
stopping of the Mode Logger the current configuration of the Mode Logger and Message Archiver services and to
and Message Archiver. change their configuration.

Refer to the following table for troubleshooting procedures:
Problem Procedure
Location of the Message 1. Locate and run the Mode Logger Control on the PC connected to the DLAN+ to
Archiver Database for a determine where the raw Mode Logger messages are being sent. (From the Mode
particular DLAN+ network is Logger control, click Setting and the Mode Logger tab. Determine the destination of
not known the Mode Logger messages from the option box Send Mode Logger messages to
Archiver either This PC or Remote PC.)
2. From the PC that is specified as the destination of the Mode Logger messages, run
Mode Logger Control (step 1), and check the Message Archiver tab for specified
Message Archiver Database Location.
3. If the Message Archiver Database is not local to the PC containing DLAN+ Status
Monitor, map to the directory (using Explorer) where the Message Archiver
Database resides.
4. Start DLAN+ Status Monitor. It will automatically attempt to connect to the last valid
Message Archiver Database that it was connected to or it will prompt the user for the
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 the
Settings/Database dialog box. DLAN+ Status Monitor will automatically begin
displaying the first DLAN+ network it finds in the Message Archiver Database. If a
different DLAN+ is to be displayed, from DLAN+ Status Monitor choose the Settings
menu and DLAN+
Set the SDB server name and The SDB server name and path are read from the Message Archiver Database and
path cannot 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 a The DLAN+ Status Monitor application compares the current data timestamp with the
gray background. (Why isnt previous data timestamp to determine if new data is being read from the Message
the data live?) Archiver database. If the timestamp changes between successive reads from the
database, the data read is considered Live, and is displayed against a green background
(possibly red or yellow in Database Drop Status mode).
If the timestamp does not change between successive reads, the data for the currently
selected DLAN+ is not being actively updated by the Message Archiver service and
displays against a gray background.
Possible causes: Message Archiver is not receiving data from Mode Logger (refer to Chapter 3).
1. Verify that Mode Logger is running (check Mode Logger status in the Mode Logger
Control application).
2. From the PC where Mode Logger is running, check the Mode Logger settings. The
location should correspond to the location of the Message Archiver Database
displayed by DLAN+ Status Monitor.
3. From the PC where Message Archiver is running, check the Message Archiver
settings. The Message Archiver Database location should correspond to the location
of the Message Archiver Database displayed by DLAN+ Status Monitor status bar.
Message Archiver is not running.

Check Message Archiver status in the Mode Logger Control program.
Problem Procedure
Possible causes continued Message Archiver is not updating the selected database.
Refer to the problem, Where is the Message Database for a particular network?
Message Archiver is not updating the data for the currently selected DLAN+.
Refer to the problem, Why are there more DLAN+ entries in the DLAN+ list than
there are DLAN+ networks in the system?
There are more DLAN+ Message Archiver was unable to connect to the SDB at some point when it started up,
entries in the DLAN+ list than creating a duplicate DLAN+ entry. Message Archiver relies on the SDB to resolve the
there are DLAN+s in the DLAN+ names based on the DLAN+ number included in the raw Mode Logger
system messages. Message Archiver uses the SDB topology to determine the DLAN+ name. If
Archiver cannot contact the SDB, it defaults the DLAN+ name to NET_X, where X is the
DLAN+ Net Number specified by the user in the Mode Logger Control application under
the Settings menu/Mode Logger page. Message Archiver creates an entry (by name) in
the Message Archiver Database for the DLAN+ if it does not already exist when
Message Archiver is started up. If SDB is unavailable when Message Archiver is started
up, multiple entries for the same network may exist in the Message Archiver Database.
The Message Archiver updates only one of those network entries 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 Database
Or
Stopping Message Archiver and using the Browse utility to delete the redundant
entries from the NETSTAT.DBF table.
DLAN+ names are incorrect, SDB is not specified correctly in the Message Archiver setup, causing the network
for example ALAN is listed as names to be defaulted to Net_X. Refer to the previous problem, Why are there more
NET_1 DLAN+ entries in the DLAN+ list than there are DLAN+s in the system.
Drop names all display as All live drops on the DLAN+ that do not have a corresponding device listed in the SDB
UNDEF in Database Drop topology are labeled as undefined. If the DLAN+ Status Monitor application cannot
Status mode connect to the SDB, all of the live drops will be labeled as undefined.
Some of the data fields Some versions of Mode Logger application do not correctly represent the data when the
display roll instead of a Mode Logger boards data values roll over. Rather than starting over at zero, the values
number become large negative numbers. Rather than display confusing and inaccurate data on
the screen, the DLAN+ Status Monitor application displays roll, where a negative value is
encountered. The Mode Logger Boards register values can only be reset by restarting
the Mode Logger service, either through the Mode Logger Control or by rebooting the
PC.
Err displayed in some of the Err displays if the value of a particular data field is too large to be displayed by DLAN+
data fields Status Monitor (such as >999G). This should never happen because the Mode Logger
data register will roll over long before a number that large occurs. However, the data in
the Message Archiver Database would be suspect in this case.

Chapter 6 Message View
Introduction
Section Page
Concepts .................................................................................................................. 6-1

Using Message View ............................................................................................... 6-3
Configuration ........................................................................................................... 6-6
Examples................................................................................................................ 6-12
This chapter provides instructions for using the Message View application to view
data collected by the Mode Logger and Data Logging applications.
Concepts
Alarms are selected messages Message View provides two modes to view alarm and event messages. It operates
that announce a device or differently, depending on which mode is specified.
process condition.
Dynamic mode reads and displays the most recent database messages.
Events are actions, such as a
command message. Static mode reads the database once and displays those messages read at that
time.
If no filter is applied, the Message View is used to define a filter with specific criteria. The filter can be
database is read periodically applied to either mode, so only messages that meet the filter criteria are displayed.
at the rate specified by the Earlier messages are removed from the database to provide room for the most recent
user in the Setting menu, events and alarms. The size of the message database (in either mode) is set in the
Update Interval. Mode Logger Control application under Settings and the tab Message Archiver
(refer to Chapter 3).
Message View provides the following features to display DLAN+ or Ethernet
messages:
Online view of messages, which are color coded to quickly identify a particular
class 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
GEH-6407 Maintenance and Diagnostics Applications Chapter 6 Message View 6-1

Data Flow
The following diagram displays data flow between Mode Logger and Message View.
* Selected message types Control Messages
CIMPLICITY HMI Project
Signal Names in
DLAN+ Message
Message
Alarm Manager
Interface Message Archiver Archiver
(GECAMS) Database
Control
Messages
SDB
CIMPLICITY Alarm API
CIMPLICITY ICN Messages

Alarm Mgr from Ethernet
(AMRP)
Message View
Mode Logger PC 1 Mode Logger PC 2
AlarmView
PCLG Assembly PCLG Assembly Optionally over Ethernet
CIMPLICITY
Alarm/Event Within a single PC
Database DLAN+ Network A DLAN+ Network B

transmitted by devices via DLAN+ or
Ethernet.
Message Colors
DLAN+ messages display in different colors and identify the class of a message as
defined in the following table. Only Mode Logger text (TXT) message colors can be
edited (see the section Set Alarm Colors).
Text Color Background Color 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.
6-2 Chapter 6 Message View GEH-6407 Maintenance and Diagnostics Applications

Using Message View
Message View 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 Message View
From the GE Control Systems Solutions program group/folder, click the
Message View icon. The Message View screen displays.
Note The Message Archiver Message Database location must be defined and the
path must be accessible before any message data will display (see the section
Configuration).
Event/Alarm toggle Toggle filter on/off Name of the Current

Dynamic/Static toggle Current Display Filter Details Display Filter
Current
Columns
Alarm and
Event messages
Filter searches
are displayed in
this screen
Status Bar
provides
specific Displays button Displays Events & Alarms Displays Filtered Displays Static or Displays the current
application descriptions and or Alarms Only or Unfiltered Dynamic Mode page number
information, user notes
as described

View Menu
The View menu provides the following commands:
A check mark displays by the
Toolbar toggles to display or hide
command name when the feature is the shortcut command buttons.
enabled and displayed.
Status Bar toggles to display or
hide the application information
that displays at the bottom of the
screen.
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.
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
Message Display in hex displays of the filter currently selected.
the currently selected message in
hexadecimal form.

Settings Menu
The Settings menu provides the following commands:
Note If the Alarm TXT Color command is grayed out, then there are currently no
alarm class entries defined in the SDB or the SDB is not accessible. Alarm Class
items must be defined in the toolbox (System Device and posted to the SDB) before
the command becomes active. Then, choose Refresh Alarm data from SDB to read
the changed data and enable the Alarm TXT Color command.
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 class information
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 is brought up to
date when in Dynamic mode.
Static Time Out allows you to specify (in

minutes) how long to remain in the Static
mode. When the time expires, the mode is
switched to Dynamic.
Define Filters allows you to define filter(s) with
specific criteria that is applied to search the
display for messages with the same criteria.
Generate Filter allows you to create a filter

based on the criteria of the currently selected
message on the screen. Then, the filter can be
edited.
Alarm TXTx Color allows you to set the color for

user defined alarms based on the alarm class
(LOW, HIGH, LL).
Display Font allows you to change the font of

the message text and column heading text. Use
monospace fonts to view the column fields
correctly. The default monospace font is
Courier New.
Print Font allows you to change the current

monospace font to a proportional font when
printing to a printer. Proportional fonts allow
more columns to display on one page.
Note Monospace characters have exactly the same width, producing characters
similar to those of a typewriter.

Configuration
Database Locations
To configure the Message Archiver database location
1. From the Settings menu, choose Message database. The Message
Archiver 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 database dialog
box displays.
Refer to the information that 2. Enter the Server Name and Path (path location on the SDB Server) to the
was entered during the SDB.
installation of CIMPLICITY
3. Click OK.
tools.

Display Settings
The appearance of the Message View screen can be configured to display specific
columns, fonts, and the update intervals.
To configure the display of columns
1. From the Settings menu, choose Column Config. The Column
Configuration dialog box displays.
Current Column displays the names of

the columns currently displayed on
screen.
Add->> allows you to add an Available
Column to the list of Current Columns.
Click on the desired column name in
the Available Column list and click
Add->>, or double-click the desired
column.
Remove->> allows you to remove a

column from the Current Columns list.
Click on the column and click
Remove->>, or double-click the
column itself.
Move Up and Move Down move items

in the column up or down. Click on the
column and then click Move Up or
Move Down.
2. Edit the columns from the Available Column list using Add->> and
Remove->>.
3. Edit the display order of the columns using Move Up or Move Down.
Use monospace fonts to view To change the display font
the column fields correctly.
1. From the Settings menu, choose Display Font. The Font dialog box
The default font is Courier
displays.
New.
2. Choose the font to use for the Message View screen.
To change the update interval
The default interval rate is 5. 1. From the Settings menu, choose Update Interval. The Update Interval
The minimum rate (and the dialog box displays.
smallest number that can be
2. Enter the Update interval (seconds) and click OK.
entered) is 1.

Operation
The following section describes other commands used during operation of Message
View.
Obtain Message Help

To obtain Help on an Alarm or Event message
From the View menu, choose Explain.
= Or from the Message View screen, double-click on an Alarm or Event
= Or press F4
The appropriate Help displays based on the type of Alarm/Event message selected.
The alarm types for specific Help are:
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 amount 1. From the Settings menu, choose Static Time out. The Static to Dynamic
of time that the screen stays in time out value dialog box displays with the default value 0.
Static mode before it reverts
2. Enter the time out value (minutes) from 0 (no time out) to 999.
back to Dynamic mode.

Define Filters
The command Define Filters is used to define display filters which control the
message data displayed on the screen. The Define Display Filter dialog box is
divided into three sections:
Filter Selection allows you to

create and delete a filter, edit the
filter name, and choose the
current display filter.
Columns Available provides a list

of available columns, which are
the source of data. 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 will change based on the
filter selected in this box.
The field Filter Selection contains the following:

Choose New Filter to create a new filter. The
default name is User Defined Filter x. X is
always the actual number of filters in the list
plus one. Edit this filter name by clicking on it
and typing a new name. The name entered
must be unique in the displayed drop down list.
Click on Current Display

Filter to assign the filter
displayed in the text box to
be used for the search
when applied.
Choose Delete Filter to delete the selected

filter in the Filter Selection text box.
Note If the deleted filter was the Current

Display Filter, then no display filter is assigned.

Add Search Values
In the Define Display Filter dialog box, the section Columns Available allows you to
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 Filter
Selection drop down text box or click New Filter.
2. From the field Columns Available, click on a display column and click Add
Where. 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 value is
applied to the filter search.
5. Repeat the Add Where selection until all search values are defined.
Display data where contains the search values for the filter. The format 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 option Display data
where, 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 right Add ( ) and Del ( ) buttons assign parentheses to group the value and control the
parenthesis must match. evaluation. Parentheses 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 ignores the case when searching.

Generate Filter
In the Settings menu, the command Generate Filter allows you to choose an alarm or
event message from the screen and generate a filter from its values.
To generate a filter
1. From the Message View screen, click on a message.
2. From the Settings menu, choose Generate Filter. The Name of Filter dialog
box displays.
3. Enter a unique name and click OK. The Define Display Filter dialog box
displays 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 Alarm TXT Color is grayed out, then either the SDB currently has no alarm
class entries defined or the SDB is inaccessible. Alarm Class items must be defined
in the toolbox before the command becomes active. Then choose Refresh Alarm data
from SDB to read the changed data.
To set TXTx alarm_class color

1. From the Settings menu, choose Alarm TXTx Color. The Alarm Class Color
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 or
Background Color button(s).
The text boxes allow you to
4. Choose a color and click OK. The text in the Normal State Color/Alarm State
view the text colors for
Color example text boxes change to the chosen color.
readability.
5. Click Clear Text Color to change the chosen Alarm Class color to the default
Both the Normal State and
colors.
Alarm State will change to the
default colors. 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 screen
without exiting the dialog box and continue to set colors for other classes in the
list.

User Defined Alarm Class
Text list read from the SDB.
These text boxes allow you to

view the chosen text colors for
readability.
The button, Clear Text Color

changes both Normal State
and Alarm State back to their
default colors. NormalState
Color = green text on black
background Alarm State
Color = yellow text on black
background
Printing Alarms and Events

To print alarms and events
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 are
printed.
Note In Static mode, use Page No (lower right corner of the Status bar) to
determine the page number when printing a single page or a range of pages.
Examples
The following section provides examples of filter searches. In all of the examples,
the filter shown in the Define Display Filter dialog box is selected as the Current
Display Filter. The screen that follows shows the results after the filter is applied.

Single Column Search
The following is a single column search. The Current Display Filter called All
Diagnostic messages will search the column ALARM_TYPE for all occurrences of
pdiag in the Dynamic mode.
The following screen displays the result of the search for all messages that have
pdiag in the ALARM_TYPE column.
Test.dvb - Message Viewer

Multiple Column Search
The following filter searches the column ALARM_TYPE for txts and the column
ALARM_ID for GN437.
The following screen displays the result of the search for all messages that have txts
in the ALARM_TYPE column and GN437 in the ALARM_ID column.

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

The following filter searches the column ALARM_TYPE for DVFLT and
ALARM_ID for drvf or oc2f.
The result of the filter search displays:

Wildcard Searches
In addition to and/or combinations, wildcard characters (the asterisk * and question
mark ?) can be used in the search string. The asterisk stands for any character or
characters that may appear in the same place. For example, in *aaaa, aaaaa*,
*aaaaa*, each question mark stands for a single character.
The following filter searches the column ALARM_TYPE for txts and the column
ALARM_MESS for the word ground.

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

Glossary of Terms
Alarms
Selected messages that announce a device or process condition
.dvb file
Message View binary (.dvb) file
device name
The device that owns the signal (usually a controller) that has been entered in the
SDB.
DLAN+ Net Number

Identifies the DLAN+ that the PCLG is connected to as defined in the SDB.
dynamic mode
Reads and displays the most recent database messages.
fault text database

Provides information for a specific fault code and device type.
message archiver database

Contains all translated DLAN+ messages and alarms from the Message Archiver.
message archiver location

The PC that hosts the Message Archiver program.
process rate
The rate the host program empties the DLAN+ message buffers in the shared memory
of the PCLG assembly.
GEH-6407 Maintenance and Diagnostics Glossary of Terms G-1

signal name
A valid point ID that equates to a Boolean signal from a controller device.
startup mode
Controls how the Mode Logger program is started.
static mode
Reads the database once and displays those messages read at that time.
static time out

The amount of time that the screen stays in static mode before it reverts back to
dynamic mode.
timestamp
A value that specifies the time data was created, modified, accessed, or received.
G-2 Glossary of Terms GEH-6407 Maintenance and Diagnostics

Toolbar Commands, 4-6
Using Diagnose, 0-1, 4-3
Using Diagnose, 4-1, 4-3
Diagnostics Examples, 4-1, 4-14
DLAN+ Status
Index Configuration, 5-1, 5-6
Database Location, 5-6
Display Size, 5-7
Menus Commands, 5-4
Toolbar Commands, 5-5
Troubleshooting, 5-1, 5-7
Using DLAN+ Status Monitor, 5-1, 5-3
DLAN+ Status Monitor, 0-1
Menus Commands, 5-4
A E
Alarm Color, 6-11 Examples
Alarms Tab, A-11 Message View, 6-1, 6-12
B F
BIOS Problems and Message Conflicts, 3-8 Fault Diagnostics, 4-16
Fault Text Database
C Mode Logger, 3-3
File Diagnostics, 4-20
Configuration
Diagnose, 4-1, 4-12
Command Line Arguments, 4-13 I
Live Diagnostic, 4-13 Installation, 0-1
DLAN+ Status, 5-1, 5-6 Computer Requirements, 2-1, 2-2
Message View, 6-1, 6-6 Destination Directory, 2-3
Database Locations, 6-6 Installing Control System Solutions, 2-1, 2-2
Display Settings, 6-7 License Key, 2-2, 2-3
Modify Serach Values, 6-10 Product Selection, 2-5
Operation, 6-8 Registration License, 2-4
Mode Logger, 3-1, 3-4 Uninstall Products, 2-5
D L
Data Flow License Key, 2-2, 2-3
Message View, 6-2 Live Diagnostic, 4-13
Database Location Live Diagnostics, 4-19
DLAN+ Status, 5-6
Destination Directory, 2-3
Diagnose M
Configuration, 4-1, 4-12 Memory Conflicts and BIOS Problems, 3-8
Diagnostics Examples, 4-1, 4-14 Menus Commands
Fault Diagnostics, 4-16 Diagnose, 4-4
File Diagnostics, 4-20 DLAN+ Status, 5-4
Live Diagnostics, 4-19 Message View, 6-4
Menus Commands, 4-4 Message Archiver
Print Options, 4-11 Settings, 3-6
Relay Ladder Diagram Options, 4-8 Message Archiver Database, 3-1, 3-3, 3-7, 4-1, 4-7, 4-9,
Screen Display Options, 4-12 4-12, 5-1, 5-3, 5-65-9, 6-6
SDB/Message Archiver Database, 4-9 Message Archiver Settings, 3-6
Settings, 4-7 Message Colors, 6-2
Signal Details, 4-10, 4-11 Message View, 0-1
GEH-6407 Maintenance and Diagnostics Index I-1

Alarm Color, 6-11 Diagnose, 4-12
Configuration, 6-1, 6-6 SDB Browser
Database Location, 6-6 Criteria Examples, A-7
Display Settings, 6-7 Signal Fields, A-1, A-13
Modify Search Values, 6-10 Signal Query Example, A-8
Operation, 6-8 Starting, A-1
Data Flow, 6-2 Tabs, A-1, A-5
Examples, 6-1, 6-12 Toolbar, A-4
Menus Commands, 6-4 SDB Browser Tabs
Message Colors, 6-2 Alarms Tab, A-11
Multiple Column Search, 6-14 NetGroups Tab, A-12
Single Column Search, 6-13 Resources Tab, A-12
Using Menus Commands, 6-4 Scale Tab, A-11
Using Message View, 6-1, 6-3 Signal Tab, A-5
Wildcard Searches, 6-17 Topology Tab, A-9
Mode Logger, 0-1 Where Used Tab, A-10
Configuration, 3-1, 3-4 SDB Utilities
Fault Text Database, 3-3 Starting the SDB Browser, A-3
Memory conflicts and BIOS Problems, 3-8 SDB/Message Archiver Database, 4-9
Message Archiver Database, 3-1, 3-3, 3-7, 4-1, 4-7, 4- Settings
9, 4-12, 5-1, 5-3, 5-65-9, 6-6 Diagnose, 4-7
Message Archiver Settings, 3-6 Message Archiver, 3-6
Modelogr.exe, 3-2 Mode Logger, 3-5
MsgArchiver.exe, 3-3 Signal Details, 4-10, 4-11
PCLG Assembly, 3-1, 3-7 Signal Fields, A-1, A-13
Settings, 3-5 Signal Query Example
Troubleshooting, 3-1, 3-9 SDB Browser, A-8
Modelogr.exe, 3-2 Signal Tab, A-5
MsgArchiver.exe, 3-3 Single Column Search, 6-13
Multiple Column Search Starting the SDB Browser
Message View, 6-14 SDB Utilities, A-3
N T
NetGroups Tab, A-12 Toolbar Commands
Diagnose, 4-6
O DLAN+ Status, 5-5
Topology Tab, A-9
Overview, 0-1 Troubleshooting
DLAN+ Status, 5-1, 5-7
P Mode Logger, 3-1, 3-9
PCLG Assembly, 3-1, 3-7

Settings, 3-7
U
Print Options Uninstall Products, 2-5
Diagnose, 4-11 Using Diagnose, 4-1, 4-3
Product Selection, 2-5 Using DLAN+ Status Monitor, 5-1, 5-3
R DLAN+ Status Monitor, 5-4
Using Message View, 6-1, 6-3
Registration License Agreement, 2-4
Relay Ladder Diagram Options, 4-8
Resources Tab, A-12
W
Where Used Tab, A-10
S Wildcard Searches, 6-17
Scale Tab, A-11

Screen Display Options
I-2 Index GEH-6407 Maintenance and Diagnostics

7R
*(,QGXVWULDO6\VWHPV
'RFXPHQWDWLRQ'HVLJQ5P
5HDGHU&RPPHQWV 5RDQRNH%OYG
6DOHP9$86$
*HQHUDO(OHFWULF&RPSDQ\ )D[
*(,QWHUQDO'&
:HZHOFRPHFRPPHQWVDQGVXJJHVWLRQVWRPDNHWKLVSXEOLFDWLRQPRUHXVHIXO
<RXU1DPH 7RGD\V'DWH ,IQHHGHGKRZFDQZHFRQWDFW\RX"
)D[1R
<RXU&RPSDQ\V1DPHDQG$GGUHVV -RE6LWH
3KRQH1R
*(5HTXLVLWLRQ1R
(PDLO
<RXU-RE)XQFWLRQ+RZ<RX8VH7KLV3XEOLFDWLRQ 3XEOLFDWLRQ1R
$GGUHVV
3XEOLFDWLRQ,VVXH5HYLVLRQ'DWH
*HQHUDO5DWLQJ
([FHOOHQW *RRG )DLU 3RRU $GGLWLRQDO&RPPHQWV
&RQWHQWV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
2UJDQL]DWLRQ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
7HFKQLFDO$FFXUDF\ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
&ODULW\ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
&RPSOHWHQHVV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
'UDZLQJV)LJXUHV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
7DEOHV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
5HIHUHQFLQJ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
5HDGDELOLW\ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
6SHFLILF6XJJHVWLRQV&RUUHFWLRQVLQIRUPDWLRQWKDWFRXOGEHH[SDQGHGRQDQGVXFK
3DJH1R &RPPHQWV
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
2WKHU&RPPHQWV:KDW\RXOLNHZKDWFRXOGEHDGGHGKRZWRLPSURYHDQGVXFK BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB

___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
2YHUDOOJUDGH&RPSDUHGWRSXEOLFDWLRQVIURPRWKHUPDQXIDFWXUHUVRIVLPLODUSURGXFWVKRZGR\RXUDWHWKLVSXEOLFDWLRQ"
6XSHULRU &RPSDUDEOH ,QIHULRU 'RQRWNQRZ &RPPHQW BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
'HWDFKDQGID[RUPDLOWRWKHDGGUHVVQRWHGDERYH
)ROGKHUHDQGFORVHZLWKVWDSOHRUWDSH
BBBBBBBBBBBBBBBBBBBBBBBBBBBB 3ODFH
VWDPS
BBBBBBBBBBBBBBBBBBBBBBBBBBBB KHUH
BBBBBBBBBBBBBBBBBBBBBBBBBBBB
*(,QGXVWULDO6\VWHPV
'RFXPHQWDWLRQ'HVLJQ5P
5RDQRNH%OYG
6DOHP9$86$
)ROGKHUHILUVW

*(,QGXVWULDO6\VWHPV
*HQHUDO(OHFWULF&RPSDQ\
5RDQRNH%OYG
ZZZ*(LQGXVWULDOFRP 6DOHP9$86$

Geh 6407 Control System Solutions (Maintenance and Diagnostics Applications)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Geh 6407 Control System Solutions (Maintenance and Diagnostics Applications)

Uploaded by

Copyright:

Available Formats

g

Control System Solutions

Control System Solutions

Printed in the United States of America.

ARCNET is a registered trademark of Datapoint Corporation.

Indicates a procedure or condition that, if not

Indicates a procedure or condition that, if not

Indicates a procedure or condition that should be

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

! caused by equipment malfunction, only adequately

The example and setup screens in this manual do

Chapter 1 Overview 1-1

Chapter 2 Installation 2-1

Chapter 3 Mode Logger 3-1

Chapter 4 Diagnose 4-1

 !"#$%$&'()*$+!!,-$./01!/# %23

 !"#$4$."--5"$61"7 423

To prevent personal injury or equipment damage caused by

How to Use this Manual

GEH-6407 Maintenance and Diagnostics Applications Chapter 1 Overview 1-1

1-2 Chapter 1 Overview GEH-6407 Maintenance and Diagnostics Applications

Note Other documents may use different conventions.

Indicates a list of related information, not procedural steps.

GEH-6407 Maintenance and Diagnostics Applications Chapter 1 Overview 1-3

Computer Requirements .......................................................................................... 2-2

Toolbox dependent applications are denoted with an *.

GEH-6407 Maintenance and Diagnostics Applications Chapter 2 Installation 2-1

Installing Control System Solutions

2-2 Chapter 2 Installation GEH-6407 Maintenance and Diagnostics Applications

Enter the License Key number.

The destination directory for

This dialog box option can

GEH-6407 Maintenance and Diagnostics Applications Chapter 2 Installation 2-3

Please read the entire

Click Yes to accept the

2-4 Chapter 2 Installation GEH-6407 Maintenance and Diagnostics Applications

You must click to the left of each

Click the product name in the left

The number beside each product

A description of each product

Products that were not purchased as part

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

GEH-6407 Maintenance and Diagnostics Applications Chapter 2 Installation 2-5

If you choose to remove all products by selecting

2-6 Chapter 2 Installation GEH-6407 Maintenance and Diagnostics Applications

Concepts .................................................................................................................. 3-1

GEH-6407 Maintenance and Diagnostics Applications Chapter 3 Mode Logger 3-1

* Selected message types Control Messages

CIMPLICITY ICN Messages

Mode Logger PC 1 Mode Logger PC 2

* Device faults and process alarms

The proper display of messages from different

Mode Logger (Modelogr.exe)

3-2 Chapter 3 Mode Logger GEH-6407 Maintenance and Diagnostics Applications

Fault Text Database

Note If a device is updated independently on a process or customer site, new fault

Message Archiver Database

GEH-6407 Maintenance and Diagnostics Applications Chapter 3 Mode Logger 3-3

Mode Logger Control .

The Mode Logger System Control window is displayed.

3-4 Chapter 3 Mode Logger GEH-6407 Maintenance and Diagnostics Applications

DLAN+ Net Number identifies the DLAN+

Process rate is the rate the host program

Message Archiver Location is the PC that

!"#$%$&'()*$+!!,-$./01!/# %23

!"#$4$."--5"$61"7 423