g

GE Industrial Systems
Publication: GEJ-7485
Original Issue Date: 2000-07-20

SPEEDTRONIC
Mark VI Turbine Control
Software Maintenance

 2001 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.
Document Identification: GEJ-7485
Technical Writer/Editor: Jeanne Barnes
Technical Content: Joseph Kirk and Douglas McCallum

This equipment contains a potential hazard of

electric shock or burn. To prevent personal injury
or equipment damage caused by equipment
malfunction, only adequately trained personnel
should install, operate, modify or maintain any
programmable machine.

Never reset the Mark VI controller alone. Always

cycle power on the VME rack.

CIMPLICITY is a registered trademark of GE Fanuc Automation North America, Inc.

Ethernet is a registered trademark of Xerox Corporation.
SPEEDTRONIC is a trademark of General Electric Company, USA.
Windows NT is a registered trademark of Microsoft Corporation.

Introduction
This quick reference guide provides a brief set of procedures
for frequently used Mark VI maintenance tasks. It presumes
that the user possesses at least a medium-level knowledge of
the software used.

Conventions
Arial Bold

Indicates the menu, the actual command or

option that is chosen from a menu, a button,
or title of a dialog box.

Indicates a procedure.

>

Indicates commands to be performed. For

example: (Functions > Modules > Pins).

Procedure

Page

To Validate, Build, and Download .......................................... 2

To add an I/O point.................................................................. 3
To add, delete, or move an I/O board ...................................... 4
To add, delete or modify application code............................... 5
If not able to modify application code ..................................... 5
To pass a signal between Mark VI controllers......................... 6
To pass a feedback signal from a Mark VI controller to
CIMPLICITY HMI................................................................ 7
To add a command from CIMPLICITY to Mark VI ............... 8
To add an alarm to the Mark VI controller .............................. 9
To enable Sequence of Events (SOE) for a contact input ...... 10
To add a PC Live Data collection to the Data Historian........ 11
To add a Capture block in Mark VI monitored by the Data
Historian ................................................................................ 12
To find where a signal is used in the Mark VI controller ...... 13
To find which devices are using a signal ............................... 13
To find any points that are forced in the controller................ 13
To access online help............................................................. 14

GEJ-7485

Mark VI Maintenance 1

Procedures
To Validate, Build, and Download
After making any change to the configuration code you must
perform the following commands for the changes to take
effect in the controller.
1.

Select Validate

2.

Select Build

3.

Select Download

Major Differences - Check

Download to memory and
Download to permanent
storage. Power to the
controller must be cycled
before the changes take
effect.
Minor Differences - Check
Download to memory and
Download to permanent
storage. The changes take
effect immediately upon
completion of the download.
Download symbols - This
box should always be
checked when downloading.

2 Mark VI Maintenance

GEJ-7485

 To add an I/O point

From the toolbox :

1.

Add a signal definition to attach to the I/O point, if one

does not already exist. (Functions > Modules > Pins)

2.

Locate the I/O point. (Hardware and I\O Definitions >

Mark VI I/O > Rack# > Slot#)

3.

Double click the I/O point to connect the signal definition

or right click the I/O point and select modify from the
pop-up menu.

4.

Under Configurations of the I/O point, make sure that

the Point is selected as Used.

5.

Set any other configuration settings necessary, based on

the input.

6.

Validate, Build, and Download the code.

Note Changes made to the configuration of the I/O point must

also be downloaded. With the right-mouse button, select the
I/O board and select Download.

GEJ-7485

Mark VI Maintenance 3

 To add, delete, or move an I/O board

From the toolbox:

1.

Locate the Rack where the modification is to be made:

R,S,T, or TMR. (Hardware and I\O Definitions > Mark
VI I/O > Rack#.)

2.

Add, delete, or modify the desired board in the selected

rack.

3.

Modify any configuration selections under the board if

necessary.

4.

Validate, Build, and Download the code to permanent

storage (this is a Major Difference: refer to page 2).

5.

Select the VCMI board and download the I/O topology

(click the right-mouse button and select Download).

6.

Power down the controller.

Power is provided by the Mark VI control panel to

various input and output devices. External sources of
power may be present in the Mark VI panel that are
NOT switched by the control power circuit breaker(s).
Before handling or connecting any conductors to the
equipment, use proper safety precautions to ensure all
power is turned off.

Some boards contain static-sensitive components. To

prevent component damage caused by static
electricity, use static-sensitive handling techniques
with all boards.
From the VME rack:

7.

Physically add, delete, or move the desired boards to

reflect the new topology.

8.

Physically add, delete, or move the associated terminal

board connections.

From the toolbox:

9.

Turn the controller power back on.

10. If a new board was added, select the board and download
the configuration (click the right-mouse button and select
Download).

4 Mark VI Maintenance

GEJ-7485

 To add, delete, or modify application code

From the toolbox:

An instanced
module is from a
Module
Definition.

1.

Locate the application code to be modified (Functions >

Modules > Tasks). Code can only reside in tasks.

2.

If the application code to be modified is under an

instanced module, the module must be overriden before
any changes can be made. (Double-click the module and
select the Override checkbox.)

3.

Modify the application code.

4.

Validate, Build, and Download the application code.

(Most code changes result in minor differences and can
be downloaded online to memory. If major differences
result, the code must be downloaded to permanent
storage and the power cycled on the unit. Refer to page 2
for more information.)

Note If adding a new module, make sure that the scheduling

period is set properly (typically all code in a Mark VI runs at
40 ms. The default for a new module is 320 ms). Double-click
on the module and set the scheduling rate.
If not able to modify application code
From the toolbox:

Make sure you have selected the proper privilege level

(Options > Privilege > 2).
Or, check the status view in the lower right hand corner of the
toolbox to see if READ is displayed in yellow. If so, this either
means that another person has the file open or the toolbox did
not perform an orderly shutdown the last time the file was
opened If it is the latter, then the Read only property must be
removed from the file before opening it in the toolbox. (Close
the toolbox, locate the file in Windows NT Explore, select
the file with the right-mouse button, select Properties, and
uncheck the Read only property).
Or, if you are trying to make a change inside a module, make
sure that it is not attached to an instanced module (it will have
a colon in the module name, such as name:). Double-click on
the module name. From the dialog box, select the override
checkbox. The symbol @ will replace the : in the module
name.

GEJ-7485

Mark VI Maintenance 5

 To pass a signal between Mark VI controllers

From the toolbox:

1.

Open the *.m6b file for controller #1.

2.

Add a signal definition if one does not already exist in

controller #1 (Functions > Modules > Pins).

3.

Add the signal to an EGD exchange (Hardware and I/O

definitions > EGD network > Exch#). Configure the point
direction as Write.

4.

Put all signals into the database (Device > Put into
database > Full).

5.

Validate, Build, and Download the application code

for controller #1 to permanent storage (this is a Major
Difference: refer to page 2).

6.

Cycle power on controller #1 rack.

7.

Open the *.m6b file for controller #2.

8.

Use the signal in the application code (Functions >

Modules > Tasks).

9.

Get all signals from the database (Device > Get from
database > Full).

10. Validate, Build, and Download the application code

for controller #2 to permanent storage (this is a Major
Difference: refer to page 2).
11. Cycle power on controller #2 rack.

6 Mark VI Maintenance

GEJ-7485

 To pass a feedback signal from a Mark VI

controller to CIMPLICITY HMI
From the toolbox:

1.

Open the controller file (*.m6b).

2.

Add a signal definition if one does not already exist

(Functions > Modules > Pins).

3.

Add the signal to an EGD exchange (Hardware and I/O

definitions > EGD network > Exch#). Configure the point
direction as Write and select a valid CIMPLICITY
resource ID.

4.

Put all signals into the database (Device > Put into
database > Full).

5.

Validate, Build, and Download the application code

for the controller (this is a Major Difference: refer to page
2).

6.

Cycle power on the controller rack.

From SDB Utilities:

7.

Import the signals from the Mark VI controller.

From the CIMPLICITY Workbench:

GEJ-7485

8.

Open the CIMPLICITY project.

9.

Stop

and start

the project.

Mark VI Maintenance 7

 To add a command from CIMPLICITY to Mark VI

controller
From the toolbox:

1.

Add a signal definition if one does not already exist

(Functions > Modules > Pins).

2.

Add the signal to an Ethernet SRTP page (Hardware

and I/O definitions > Ethernet SRTP Interface > Pg#).
Configure the direction as Read and select a valid
CIMPLICITY resource.

3.

Put all signals into the database (Device > Put into
database > Full).

4.

Validate, Build, and Download the application code

for the controller (this is a Major Difference: refer to page
2).

5.

Cycle power on the controller rack.

From SDB Utilities:

6.

Import the signals from the Mark VI controller.

From the CIMPLICITY Workbench:

7.

Open the CIMPLICITY project.

8.

Stop

and start

the project.

If this is a Simplex system, the procedure is complete.

9.

If this is a TMR system you must duplicate the new

signals in the device to the R, S, and T controllers.
(Equipment > Devices > unit name ex G6.)
a.

Click on the signal name with the right-mouse button

and select Duplicate.

b.

Rename the signal to G6\R\SIGNAME and enter the

device name as G6_R.

c.

Repeat for S and T controllers.

10. Stop and start the project.

11. Enter Yes to update the project

8 Mark VI Maintenance

GEJ-7485

 To add an alarm to the Mark VI controller

From the toolbox:

1.

Add a signal definition if one does not already exist

(Functions > Modules > Pins).

2.

Write application code to generate the alarm with the

alarm signal definition as the output.

3.

Attach the alarm signal definition to an alarm group block

(ALMGRP).

4.

Validate, Build, and Download the application code to

the controller.

From the F:\unit* file (Alarm.dat):

5.

Edit the Alarm.dat file. Enter the alarm text to be

displayed. Be sure to edit the correct entry.

From the CIMPLICITY Workbench:

6.

Open the CIMPLICITY project.

7.

Stop

the CIMPLICITY project.

From the Windows Control Panel:

8.

Select Services.

9.

Stop and start the TCI (Turbine Control Interface).

From the CIMPLICITY Workbench:

10. Run

GEJ-7485

the CIMPLICITY project.

Mark VI Maintenance 9

 To enable Sequence of Events (SOE) for a contact

input
From the toolbox:

1.

Locate the I/O point. (Hardware and I\O Definitions >

Mark VI I/O > Rack# > Slot#)

2.

Under Configuration of the I/O point, make sure that

SOE is Enabled.

3.

Download the configuration to the I/O board (Select the

board using the right-mouse button and select
Download).

From DOS:

4.

Open a command prompt and change directory to

F:\unit*

5.

Type DDBUILD2.EXE to update UNITDATA.DAT

with the signal name attached to the SOE contact input.

From the CIMPLICITY Workbench:

6.

Stop

the CIMPLICITY project.

From the Windows Control Panel:

7.

Select Services.

8.

Stop and start the TCI (Turbine Control Interface).

From the CIMPLICITY Workbench:

9.

Run

10 Mark VI Maintenance

the CIMPLICITY project

GEJ-7485

 To add a PC Live Data collection to the Data

Historian
From the toolbox:

1.

Add all signals to be collected to the EGD page if they do

not exist already. Make sure the point direction is Write
and you have entered a valid CIMPLICITY resource ID.
If all of your signals already exist on the EGD page, go to
step 8.

2.

Put the new signals into the database. (Device > Put into
database > Full)

3.

Validate, Build, and Download the code to the

controller.

From SDB Utilities:

4.

Import the signals from the Mark VI device

From the CIMPLICITY Workbench:

5.

Open the CIMPLICITY project.

6.

Stop

and start

the project.

From the toolbox:

7.

Open the Data Historian configuration file (*.reb)

8.

Add a new collection by selecting Data Historian PC

Live Data.

9.

Enter the network name and other configuration

parameters.

10. Add signal names under this collection.

11. Get signals from the database. (Device > Get Signals)
12. Validate, Build, and Download to the Data Historian.
Data Historian Service must be running for Download to
complete successfully.
The collection can be viewed under the C:\Historian_data
directory, located on the same PC as the Data Historian.

GEJ-7485

Mark VI Maintenance 11

 To add a Capture block in the Mark VI controller,

monitored by the Data Historian
From the toolbox:

1.

Add a Capture block in the Mark VI application code.

2.

Configure the Capture block. Make sure you have

attached a signal to the status output pin.

3.

Add this signal to the EGD page. Make sure the point
direction is Write and you have entered a valid
CIMPLICITY resource ID.

4.

Put the new signals into the database. (Device > Put into
database > Full)

5.

Validate, Build, and Download to the controller.

6.

Cycle the power if you had Major Differences and had to

download to permanent storage (refer to page 2).

From SDB Utilities:

7.

Import the signals from the Mark VI controller.

From the CIMPLICITY Workbench:

8.

Open the CIMPLICITY project.

9.

Stop

and start

the project.

From the toolbox:

10. Open the Data Historian configuration file (*.reb)

11. Add a new collection by selecting Controller Capture
Buffer.
12. Enter the network name and other configuration
parameters.
13. Add the signal name that references the Capture block
status output pin. This signal must be added to the EGD
page going to the PC where the Data Historian is located.
14. Get signals from the database. (Device > Get signals)
15. Validate, Build, and Download to the Data Historian.
Data is collected the next time the Capture block is
triggered.
Data can be viewed under the C:\Historian_data directory
located on the same PC as the Data Historian.
12 Mark VI Maintenance

GEJ-7485

 To find where a signal is used in the Mark VI

controller
From the toolbox:

Open the Finder

and select the correct tab.

The Finder is used to locate signal usage in the MarkVI

controller. An asterisk (*) in front of any line indicates
that the signal is being written to that location.
To find which devices are using a signal
From the toolbox:

Select the View menu and SDB Browser.

To find any points that are forced in the controller

From the toolbox:

GEJ-7485

Select the View menu and Force Lists.

Mark VI Maintenance 13

 To access online help

Online help exists for all standard and turbine (industry)
specific blocks. For example, from the Help menu (shown
below) find help on errors encountered while downloading
under Runtime Errors. Help can typically be found on any
selected item by simply pressing F1.

If your help files do not work, select the Options menu and
Settings, and the tab Directories. Make sure that the Mark
VI controller product library is set to C:\Program Files\GE
Control System Solutions\MarkVI.

Related Publications
In addition to this quick reference guide, other related
publications are available as follows:

GEH-6403, Control System Toolbox for Configuring a

Mark VI Turbine Controller

GEI-100278, Data Historian Users Guide

14 Mark VI Maintenance

GEJ-7485

*(,QGXVWULDO6\VWHPV
*HQHUDO(OHFWULF&RPSDQ\



5RDQRNH%OYG

ZZZ*(LQGXVWULDOFRP

6DOHP9$86$