u0-1801 iiu/ethernet/general electric mark v interface

IIU/Ethernet/General Electric Mark V InterfaceUser’s Guide

1-11-3 1-4

2-12-12-2-2-3-5

-7-9

3-13-13-1

4-1-2

-22-48-15

Section 1. Introduction

1-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2. Contents of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3. Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2. Hardware

2-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2. WDPF Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3. General Electric Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4. Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2-4.1. Fully Redundant System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4.2. Redundant System with Non-Redundant GE Stagelink Cable . . . . . . . . . . 22-4.3. Redundant System with Non-Redundant <G> Node and General Electric

Stagelink Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4.4. Non-Redundant System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Section 3. Software Installation

3-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2. Interface Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3. Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4. Software Configuration

4-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2. Software Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4-2.1. Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-2.2. General Information About the Configuration File . . . . . . . . . . . . . . . . . . . 4-4-2.3. Configuration File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44-2.4. Configuration File Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-

4-3. Point Record Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

9/98 i U0-1801Westinghouse Proprietary Class 2C

Table of Contents, Cont’d

Section Title Page

5-15-5-22-2

-3-4-7-5-7-7-8

-1-2

-1-2

Section 5. Software Startup and Operation

5-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2. Software Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3. Software Operation (Data Exchange Functions) . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-3.1. Periodic Data from General Electric to WDPF . . . . . . . . . . . . . . . . . . . . . . 5-5-3.2. Sequence of Events (SOE) from General Electric to WDPF. . . . . . . . . . . . 55-3.3. Digital Logic Events from General Electric to WDPF . . . . . . . . . . . . . . . . 5-35-3.4. Commands from WDPF to General Electric . . . . . . . . . . . . . . . . . . . . . . . . 55-3.5. Alarms and Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55-3.6. Sequence of Events Timing Considerations . . . . . . . . . . . . . . . . . . . . . . . . 5

5-4. Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575-4.1. Error and Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4.2. Failures and Backup Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55-4.3. Drop Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Appendix A. Configuration File

A-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AA-2. Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A

Appendix B. Guidelines for System Integration

B-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BB-2. Common Integration Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B

Glossary

U0-1801 ii 9/98Westinghouse Proprietary Class 2C

9/98 iii U0-1801

Table of Contents, Cont’dList of Figures

Figure Title Page

Westinghouse Proprietary Class 2C


1-1. Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Section 2. Hardware

2-1. Cable Connection Diagram for a Fully Redundant System. . . . . . . . . . . . . . . . . . . 2-4 2-2. Cable Connection Diagram for a Redundant System with Non-Redundant

General Electric Stagelink Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2-3. Cable Connection Diagram for Redundant System with Non-Redundant

<G> Node and General Electric Stagelink Cable . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 2-4. Cable Connection Diagram for a Non-Redundant System . . . . . . . . . . . . . . . . . . 2-10


3-1. iSBC386sx Jumper Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 3-2. iSBC272 VGA Adapter Jumper Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 3-3. IIU Transition Connector Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 3-4. Sample HOSTS File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9


5-1. Sample GSMSTART.CMD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

9/98 iv U0-1801

Table of Contents, Cont’dList of Tables

Table Title Page



1-1. Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4


3-1. iSBC386sx CMOS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 3-2. Hard Disk Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 3-3. Ethernet Node Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 3-4. General Electric Mark V Interface Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10


4-1. IIU/Ethernet/Mark V Configuration File Parameters . . . . . . . . . . . . . . . . . . . . . . . 4-4 4-2. Valid WDPF Record Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13


5-1. Alarm Management from WDPF to General Electric . . . . . . . . . . . . . . . . . . . . . . . 5-4 5-2. Alarm Management from General Electric to WDPF . . . . . . . . . . . . . . . . . . . . . . . 5-5 5-3. Drop Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Appendix B. Guidelines for System Integration

B-1. Sample Interface Configuration File Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

se

t

rica

ber


1-1. Section Overview

This document describes the operation of the WDPF® Intelligent Interface Unit(IIU)/Ethernet/General Electric SPEEDTRONIC™ Mark V Turbine ControlInterface (hereafter referred to as the Mark V Interface).

An IIU is a personal computer on a Multibus®card which has access to the databaof the Distributed Processing Unit (DPU). The Mark V Interface allows anexchange of data between the WDPF Westnet II™ Data Highway and the GeneralElectric Mark V Turbine Control. In the past, communication between thesesystems was accomplished via an RS-232 serial connection. Now, however,communication takes place via an Ethernet network connection. The Etherneconnection offers two advantages over the serial connection:

1. Faster connection (through the network) leads to greater throughput.

2. Additional functions are available.

The MarkV Interface makes exchange of the following types of data possible:

• Periodic data from General Electric to WDPF

• Event-driven data from General Electric to WDPF

— Sequence of events (SOE) from General Electric to WDPF

— Digital inputs from General Electric to WDPF

— Alarms from General Electric to WDPF

• Commands from WDPF to General Electric

— WDPF managing General Electric alarms

— Pushbutton and setpoint targets from WDPF to General Electric

The network protocol is TCP/IP, which allows reliable transportation of linkmessages. The application protocol is General Electric’s GSM (General ElectDrive Systems (GEDS) Standard Messages). GSM messages are passed to TCP/IP program, which sends them over the network to the General Electricsystem. Refer to “GEDS Standard Messages Format (GSM),” document numGEI-100165, for more information about GEDS Standard Messages.Figure 1-1illustrates how data flows between the IIU and the Mark V systems.

9/98 1-1 U0-1801Westinghouse Proprietary Class 2CWestinghouse Proprietary Class 2C

Figure 1-1. Data Flow Diagram

Westnet II Data Highway

WDPF IIU Database

WDPF- Mark V Interface Program

General Electric GSM Server Program

General Electric Mark V Database

GSM

TCP

IP

Ethernet

GSM

TCP

IP

Ethernet

Ethernet HardwareInterface CardsTransceiversCablesTerminators

ApplicationProtocol

NetworkProtocol

PhysicalLink

via Stagelink

IIUDrop

GeneralElectric

<G> Node

U0-1801 1-2 9/98Westinghouse Proprietary Class 2CWestinghouse Proprietary Class 2C

1-2. Contents of This Document

w

n

1-2. Contents of This Document

This document is organized into the following sections:

Section 1. Introductionprovides an overview of the Mark V Interface.

Section 2. Hardwaredescribes the hardware required for theIIU/Ethernet/ Mark V Interface.

Section3.SoftwareInstallation discusses the required interface software and hoit is installed.

Section 4. Software Configurationdiscusses the configuration file used by theMark V Interface.

Section 5. Software Startup and Operationdiscusses the interface softwarefunctions.

Appendix A. Configuration File shows an example of a complete configuratiofile.

Appendix B. Guidelines for System Integrationdiscusses questions that mayarise during system integration.


1-3. Reference Documents

ser

rithmof

d

.

ides

r

s

s,


Additional reference documents that may be helpful to the Mark V Interface uare listed inTable 1-1.

Table 1-1. Reference Documents

Document Number Title Description

U0-0131 Record Types User’s Guide Describes point, system, and algorecord types and the purpose and usethe records.

U0-0281 Engineer Station SupportUtilities

Describes disk management, pointdirectory maintenance, andmiscellaneous functions. Commandsfor manipulating disks, directories, anfiles are described.

U0-1280 Operator Station User’s Guide Describes capabilities of StandardOperator Station for monitoringprocesses controlled by WDPF system

U0-2101 Clock Interface Unit User’sGuide

Describes Clock Interface Unit (CIU).Provides information on configurationand operation.

U0-2111 True Time CIU User’s Guide Describes the True Time CIU. Provinformation on configuration andoperation.

U0-2400 Introduction to PCH User’sGuide

Describes WDPF Personal Computeon Westnet II Data Highway (PCH).Describes hardware and softwareconfigurations required to transformIBM PS/2 personal computer into aPCH.

U0-2425 PCH System MonitoringFunctions User’s Guide

Describes system monitoring functionperformed by a PCH, including analarm system that reports malfunctionconducting point reviews, andprocessing and displaying GeneralMessages.

U0-1801 1-4 9/98Westinghouse Proprietary Class 2CWestinghouse Proprietary Class 2C

n

s

e

U0-2480 Introduction to ISA-PCHUser’s Guide

Describes configuration and use of aISA-PCH.

U0-2481 ISA-PCH System MonitoringUser’s Guide

Describes system monitoring functionperformed by an ISA-PCH.

U0-8100 Operator WEStation User’sGuide

Describes the use of OperatorWEStation windows for viewing andcontrolling the current status of plantprocess control systems.

U0-8500 WEStation Historian (HSR)User’s Guide

Describes the functions and use of thHSR.

GEI-100165 GEDS Standard MessagesFormat (GSM)

Describes General Electric’s GSMmessages.

PC/TCP Network Software forOS/2 Installation andConfiguration Guide, Version1.3 or later.

Describes how to install the networksoftware.

GEH-6195, Rev. B Chapter 11- Ethernet &TCP-IP Describes General Electric’sapplication as it relates to the operator interface.

Table 1-1. Reference Documents (Cont’d)

Document Number Title Description

ded

ator

Section 2. Hardware


This section describes the hardware required for the Mark V Interface. It is diviinto the following sections:

• WDPF Hardware (Section 2-2)

• General Electric Hardware (Section 2-3)

• Hardware Configuration (Section 2-4)

2-2. WDPF Hardware

The Mark V Interface runs on an IIU drop with an Ethernet adapter. The operconsole can be a PCH (described in “PCH System Monitoring Functions User’sGuide,” U0-2425), a standard Operator Station (described in “Operator StationUser’s Guide,” U0-1280), or an Operator WEStation (described in “OperatorWEStation User’s Guide,” U0-8100).

The WDPF hardware required for the IIU drop is:

• DPU on the Westnet II Data Highway

— Includes PROMS with TCU patch

• iSBC386sx Multibus card with VGA adapter

• Hard disk and floppy drive

• iSBX586 Ethernet adapter

• Ethernet transceiver and transceiver cable

To configure the system, the following are also needed:

• VGA monitor

• AT-style keyboard

• PS/2-style mouse with 9-pin D connector (optional)

1/98 2-1 U0-1801

2-3. General Electric Hardware

c

ntrateallyteilsicatendthe

er,

ly

2-3. General Electric Hardware

The General Electric hardware required for the Mark V Interface is:

• <G> node

• Connecting cable (10Base2 Ethernet cable)

• Mark V communication processor (either <C> or <D>)

A <G> node communicates with the Mark V controls over the General ElectriStagelink through a Mark V communication processor (either <C> or <D>).

2-4. Hardware Configuration

On the Westinghouse side, the Mark V Interface is configured to use redundaDPUs. This configuration uses two DPUs, IIU primary and partner, with a sepaEthernet link from each DPU to the General Electric system. The interface normcommunicates with the primary IIU. If the primary IIU is unable to communicawith the <G> node or the Mark V controls (due to error or failure), then the IIU faover and communicates with the partner IIU. The partner continues to commununtil it detects a failure. When the IIU is in backup, it monitors communication areports a drop fault if it cannot communicate with the <G> node processor or Mark V controls.

The Mark V Interface can be configured with one non-redundant DPU; howevnon-redundant configuration is not recommended for systems that will beperforming control.

On the General Electric side, the Mark V Interface can be configured as a fulredundant system, or partially redundant, depending on which elements areredundant. Configuration variations include the following:

• Fully redundant system (Section 2-4.1)

• Redundant system with non-redundant General Electric Stagelink cable(Section 2-4.2)

• Redundant system with non-redundant <G> node and General ElectricStagelink cable (Section 2-4.3)

• Non-redundant system (Section 2-4.4)

U0-1801 2-2 1/98

f the

d oneV

ofpters

2-4.1. Fully Redundant System

In a fully redundant communication system, each side of the system consists oWestnet II Data Highway, one redundant DPU (IIU primary or partner) with itsiSBC386sx card and Ethernet adapter, one Ethernet cable, one transceiver antransceiver cable, one <G> node processor, one Stagelink cable to the Mark controls and all of the Mark V communication processors (either <C> or <D>nodes). In order for full communication to take place, all of the parts for one sidethe redundant system must be in place. For example, if one of the Ethernet adafails and one of the <D> node processors on the other system fails, then fullcommunication is not possible. The redundancy will only tolerate one failure.

Figure 2-1 illustrates the cable connections for a fully redundant system.

1/98 2-3 U0-1801

Figure 2-1. Cable Connection Diagram for a Fully Redundant System

Westnet II Data Highway To Other WDPF Drops

IIUPrimary

IIUPartner

General Electric StagelinkTo Other Mark V Controlsand Nodes

<C> <D> <C> <D>

<G>

Mark VControl

Mark VControl

TransceiversEthernet Cables(10BASE2)

Terminator

TerminatorTerminator

Terminator

<G>

U0-1801 2-4 1/98

rdcable,elink

2-4.2. Redundant System with Non-Redundant GE Stagelink Cable

In a redundant communication system with non-redundant General ElectricStagelink, each side of the redundant system consists of the Westnet II DataHighway, one redundant DPU (IIU primary and partner) with its iSBC386sx caand Ethernet adapter, one Ethernet cable, one transceiver and one transceiverand one <G> node processor. The non-redundant elements include one Stagcable to the Mark V controls and all of the <C> node processors.

Figure 2-2 illustrates the cable connections for a redundant system withnon-redundant General Electric Stagelink cable.

1/98 2-5 U0-1801

Figure 2-2. Cable Connection Diagram for a Redundant System with Non-RedundantGeneral Electric Stagelink Cable


IIUPrimary

IIUPartner

General Electric Stagelink

To Other Mark V Controlsand Nodes

<C>

<G>

Mark VControl

TransceiversEthernet Cables(10BASE2)

Terminator

TerminatorTerminator

Terminator

<G>

<C>

Mark VControl

U0-1801 2-6 1/98

eralstnetsx

r, andode

2-4.3. Redundant System with Non-Redundant <G> Node and GeneralElectric Stagelink Cable

In a redundant communication system with non-redundant <G> node and GenElectric Stagelink cable, each side of the redundant system consists of the WeII Data Highway, one redundant DPU (IIU primary and partner) with its iSBC386card and Ethernet adapter, one transceiver and one transceiver cable. Thenon-redundant elements consist of one Ethernet cable, one <G> node processoone General Electric Stagelink cable to the Mark V controls and all of the <C> nprocessors.

Figure 2-3 illustrates the cable connections for a redundant system withnon-redundant <G> node and General Electric Stagelink cable.

1/98 2-7 U0-1801

Figure 2-3. Cable Connection Diagram for Redundant System with Non-Redundant <G>Node and General Electric Stagelink Cable


IIUPrimary

IIUPartner



<C>

<G>

Mark VControl

Transceivers

Ethernet Cable(10BASE2)

Terminator

Terminator

<C>

Mark VControl

U0-1801 2-8 1/98

ata

essor,C>

2-4.4. Non-Redundant System

A non-redundant communication system consists of a redundant Westnet II DHighway, one DPU (IIU) with its iSBC386sx card and Ethernet adapter, onetransceiver and one transceiver cable, one Ethernet cable, one <G> node procand one General Electric Stagelink cable to the Mark V controls and all of the <node processors.

Figure 2-4 illustrates the cable connections for a non-redundant system.

1/98 2-9 U0-1801

Figure 2-4. Cable Connection Diagram for a Non-Redundant System


IIU



<C>

<G>

Mark VControl

Transceiver

Ethernet Cable(10BASE2)

Terminator

Terminator

<C>

Mark VControl

U0-1801 2-10 1/98

ed

er

at the

is



This section discusses installation of the Mark V Interface software. It is dividinto the following sections:

• Interface Software (Section 3-2)

• Installation Procedure (Section 3-3)

3-2. Interface Software

The Mark V Interface consists of the following software elements:

• OS/2™ Operating System, Version 2.0 or later

• PC/TCP Network Software for OS/2 from FTP Software, Version 1.3 or lat

• WDPF- General Electric Mark V Interface Software

3-3. Installation Procedure

Use the following procedure to install the interface software:

1. The jumpers on the iSBC386sx and iSBC272 boards should have been setWestinghouse factory. If the iSBC386sx board is not working or if areplacement board is being installed, refer toFigure 3-1 for proper jumpersettings.

If the iSBC272 VGA adapter board is not working or if a replacement boardbeing installed, refer toFigure 3-2 for proper jumper settings.

Note

The information in these drawings could besuperceded by information in the hardwarekit drawing (#3A59342).

9/98 3-1 U0-1801Westinghouse Proprietary Class 2C


Figure 3-1. iSBC386sx Jumper Setup

Detail A Detail BDetail C

Detail G

Detail D

Detail EDetail F

MB Timeout

E107 E108

INIT* Drive

E134

E136

Detail A

E12E22E31

E13E23E32

EPROMS

E5E14E24

E11E21E30

UniversalByte-wide Sites

Detail B

E33E45E24

E42E54

E64

Local Interrupt Matrix

Detail C

SpeakerE43E55

E44E56

Test-modeEnable

E73E81E88E92

E103

E78E76E84E91E95

E77

E106E87

E85

E66 E68387TMSXTMError

Multibus/ISAI/O

SBX

CPU

MathChipSocket

PasswordE3

E4E5

U0-1801 3-2 9/98Westinghouse Proprietary Class 2C


Figure 3-1. iSBC386sx Jumper Setup (Cont’d)

Detail D

E70

E71

E72

E69

E80

ACLO

E79

Watchdog Timer

Watchdog Timer

E97 E99

E98

Detail E

E132

E133

E135

E129 E131

CBRQ

E137

BCLK

CCLK

E113

E117

E122

E127

E114

E119

E124

E128

Multibus OutputInterrupt Matrix

Detail F

E109

E111

E115

E120

Multibus Address

E125

E110

E112

E116

E121

E126

Detail G



Figure 3-2. iSBC272 VGA Adapter Jumper Setup

E4

E6

E8

E10

E12

E5

E7

E9

E11

E13

E24

E26

E25



n of

hen the

2. Run the iSBC386sx setup program. If the battery-backed setup configuratiothe iSBC386sx board has not been initialized at the factory or has beencorrupted, perform the following steps to initialize the parameters:

a. Connect a monitor and keyboard to the iSBC386sx board using theconnectors on the transition connector panel. SeeFigure 3-3. Reset theIIU/DPU at the power supply.

b. The iSBC386sx will go through its Power On Self Test (POST). While tPOST is running, the address of the memory being tested is displayed oscreen. As soon as the POST finishes, repeatedly hitctrl-alt-insert

until the setup utility starts.

c. Set the parameters as shown inTable 3-1. After all the options are enteredand saved, reset the IIU/DPU using the power supply reset button.

Figure 3-3. IIU Transition Connector Panel

PRI

KBD MOU COM2 LPT1 A

Connect AT-style keyboard at KBD.Connect VGA monitor at VGA.Connect 9-pin PS/2-style mouse at MOU (optional).Connect Ethernet transceiver at A.

VGA COM1 KBDMOUCOM2LPT1A VGACOM1

SEC



Table 3-1. iSBC386sx CMOS Parameters

Parameter Setting

First Page:

Time Set to current time

Date Set to current date

Diskette A 3.5 inch, 1.44 MB

Diskette B Not installed

Hard Disk 1 Type 2 (SeeTable3-2 for hard diskparameters)

Hard Disk 2 Not installed

Base Memory 640 KB

Extended Memory 7168 KB

Display VGA/EGA

Keyboard Not installed

CPU speed Turbo

Second Page:

Enter Setup Pre-boot

Speaker Disabled

Primary Video Display Color

Onboard Peripherals Onboard floppy and winchesterenabled

Password Not installed

Parallel Port LPT1

Serial Port 1 COM1

Serial Port 2 COM2

Console Redirection toCOM1

Disabled

Console Redirection toCOM2

Disabled



.

movetiveit on

size

3. Set the hard disk parameters according to the type of drive on the systemChoices are shown inTable 3-2. If the hard drive is not listed, use thedocumentation that came with the drive to determine parameters.

Some hard drives have the parameters printed on the label on the drive. Rethe outer case of the drive assembly and look underneath the gray protecpaper to view the label. For future use, make a copy of the label and put the outside of the drive assembly case.

When entering the parameters for the drive, the setup program returns theof the disk in MB. For drives with more than 999MB of storage, the setupprogram returns “***” in the size field, since the size field is only threecharacters wide. This is normal and does not cause any problems.

Third Page:

Shadow BIOS ROM System BIOS

User Definable Drive Types 2 and 3

Base Memory above 512K Enabled

Offboard Video Shadow Disabled

Memory Roll Enabled

Table 3-2. Hard Disk Parameters

HardDiskType CYL HD PRE LZ SEC SIZE

FujitsuM2614ET

667 16 0 0 33 171

QuantumLPS240

723 13 0 0 51 234

QuantumLPS270

944 14 0 0 40 258

QuantumLPS365AT

976 12 0 0 61 348

SeagateST51080A

2100 16 0 0 63 ***

Table 3-1. iSBC386sx CMOS Parameters (Cont’d)

Parameter Setting


/2.

atis

ms.s to

and a

name

e if

tive, or

de

4. Install OS/2, Version 2.1, or later. Follow the directions that come with OSDefault options are good for most choices except the following:

a. Do not install Boot Manager or Dual Boot.

b. Format ALL partitions for HPFS.

c. When setting up partitions, make the first partition (which is the C drive)least 120 MB and no more than 500 MB. Install OS/2 on this partition. Thpartition is also used for the network software and the interface prograFor drives which are larger than 500 MB, the advanced installation needbe selected so that the partitions can be setup this way.

d. Select “No Printer” for the printer.

5. Plan the Ethernet. Assign an Internet Protocol (IP) address, a host name,domain name to each Ethernet node. Each <G> node and each half of aredundant IIU is an Ethernet node.The IP address, host name and domainare described inTable 3-3.

a. The IP address can be as inTable 3-3, where the address is 192.1.1.xxx,where xxx ranges from 1 to 254 and is unique for each node.

b. The host name should be unique for each node. It should be descriptivpossible. For example, drop54.

c. The domain name should be the same for each node in the system. InTable3-3, site.com is the domain name. Choose an appropriate descripand simple domain name for the system such as duke.com, unit3.commartin_station.com.

Table 3-3. Ethernet Node Requirements

Requirement Example Notes

IP Address 192.1.1.33 Unique for eachEthernet node

Host Name drop140 Unique for eachEthernet node

Domain Name site.com Same for each Ethernet no

uld betric

f the

ed

bee in

them.

6. After the IP address, host name, and domain name are selected, they shoentered in the HOSTS file. All Ethernet nodes (including the General Elec<G> nodes) should have a HOSTS file. This file should contain all the IPaddresses, host names, and domain names of all the <G> nodes and all oDPUs, even if they are not connected to the same Ethernet.Figure 3-4 is asample HOSTS file. (“#” begins a comment line.)

a. A copy of this file should exist in all Ethernet nodes, including<G>nodes. On the IIU, this file is usually called HOSTS and is locatin the C:\PCTCP\ETC directory.

b. The IP addresses and host names of all the Ethernet nodes shoulddifferent. Each node should be configured with an address and namthe HOSTS file.

c. The domain name should be the same as the domain indicated in HOSTS file. In the sample HOSTS file, the domain name is site.co

.

# This first line is always here.127.0.0.1 local host#

# IP addr host name aliases#--------- -------------- -----------# first the <G> nodes192.1.1.1 g1.site.com g1192.1.1.2 g2.site.com g2192.1.1.3 g3.site.com g3 gnode192.1.1.4 g4.site.com g4

# now the DPUs192.1.1.33 drop140.site.com drop140 dcs1192.1.1.34 drop190.site.com drop190 dcs2192.1.1.35 drop142.site.com drop142 dcs3192.1.1.36 drop192.site.com drop192 dcs4

Figure 3-4. Sample HOSTS File


de in

me

o that

ve

ent

warelts.

ies,the

put

7. Install PC/TCP Network Software for OS/2 following the directions in theInstallation Guide provided with the software. Defaults are good on mostchoices. When installing the PC/TCP software, it is important to do thefollowing:

a. Install the software on the C drive.

b. Check the box to have the installation program update CONFIG.SYS.

c. The netmask should be 0xFFFFFF00.

d. Do not use nameservers. Leave the nameservers entry box empty.

e. Enter the IP address, host name and domain name selected for the noStep 5.

f. Under Miscellaneous Applications, set the time zone to the applicable tizone.

g. Under the Server Programs (daemons) section, uncheck all the boxes snone of the daemons run.

h. Under the Kernel section, set the following:

TCP receive space = 8192TCP send space = 8192Number of 2K buffers = 70

8. Install the General Electric Mark V Interface Software and drivers.

a. Put the General Electric Mark V Interface distribution disk in the A: driof the IIU.

b. Open an OS/2 window or full screen session. Make the A: drive the currdrive.

c. At the OS/2 command prompt, enter ‘mkv-inst ’.

d. When the menu appears on screen, enter ‘I’ to install the software.

e. The installation program prompts the user to enter pathnames for softinstallation. Enter a new pathname, or press enter to accept the defau

f. The installation program then copies the files to the appropriate directorand creates ‘GSMSTART.CMD’. The user is then prompted to update WPShell desktop. The desktop must be updated at some time in order to‘GSMSTART.CMD’ in the startup folder.



or

the

The files installed are listed inTable 3-4.

g. When the menu reappears, enter ‘Q’ to quit the install program. The installprogram can be re-run at a later time to recreate the ‘GSMSTART.CMD’to update the desktop.

9. Edit the CONFIG.SYS file on the root directory of the OS/2 boot drive usingOS/2 system editor.

E config.sys

a. Verify that these following lines are in the CONFIG.SYS file:

rem -------------------------------------------pauseonerror = NO

rem -------------------------------------------rem for dpu shared memory accessDEVICE = C:\WDPF\HIGHWAY\DMA2.SYS

rem -----------------------------------------rem for pc/tcp & sbx586 cardSET TZ=EST5EDTDEVICE=c:\pctcp\drv\PROTMAN.OS2 /I:c:\pctcp\drvDEVICE=c:\PCTCP\DRV\SBX586.SYS

DEVICE=c:\pctcp\drv\SOCKET.OS2SET PCTCP=c:\PCTCP\ETC\PCTCP.INIrem -------------------------------------------

The only lines that may need to be modified or added are:

Table 3-4. General Electric Mark V Interface Software

File Default Installed Directory

gsm32.exe c: \wdpf\dl\gemarkv

gsmproc.ex c: \wdpf\dl\gemarkv

iiu_mgr.exe c: \wdpf\highway

iiu_mgr.ico c: \wdpf\highway

gsmstart.cmd c: \wdpf\dl\gemarkv

protocol.ini c: \pctcp\drv

sbx586.sys c: \pctcp\drv

dma2.sys c: \wdpf\highway

sample.cfg c: \wdpf\dl\gemarkv



theyns.

e is

.

d in

tory

ehe

pauseonerror = NO

DEVICE = C:\WDPF\HIGHWAY\DMA2.SYS

DEVICE=c:\PCTCP\DRV\SBX586.SYS

The other lines should have been added by the network software. Note:may be slightly different than shown, depending on the installation optio

For more information on the CONFIG.SYS file, refer to “Introduction toPCH User’s Guide” (U0-2400).

10. Create the database point mapping configuration file (SeeSection 4-2 fordirections on how to create a configuration file.) Once the configuration filcreated, put it in theC:\WDPF\DL\GEMKV directory.

11. Recreate the startup batch file,GSMSTART.CMD .

a. Open an OS/2 window or full screen session.

b. Make the Mark V directory the current directory(default is c: \wdpf\dl\gemkv).

c. At the OS/2 command prompt, enter ‘mkv-inst ’.

d. When the menu appears on the screen, enter ‘c’ to change the default paths

e. Pressenter to accept paths that do not change. When prompted for thedirectory and name of the configuration file, change it to the file createStep 10 (for example, c: \wdpf\dl\gemkv\fpl.cfg).

f. Accept the new settings. When the menu appears,enter ‘m’ to make theGSMSTART.CMD file.

g. When the menu appears,enter ‘Q’ to quit.

12. Load the DPU database. Update the point directory.

13. Transfer the point directory file from the Engineer’s Station to the IIU.

a. If the system is WEStation based, one way of transferring the point direcfrom the WEStation Engineer’s console (SS) to the IIU is as follows:

1) Sign out spd.online

2) Use the DOSCP command with the -b (Binary) switch to transfer thfile to a DOS 3-1/2 inch floppy with the file structure maintained. At tUNIX command prompt, enter ‘%DOSCP -b spd.online a: spd.on ’.



t

Note

If the spd.online file is larger than the floppy diskcapacity, compress the file on the WEStation anduncompress it on the IIU. Utilities are available forboth UNIX and OS/2 to perform this task.

b. If the system is based on a Standard Engineer’s Station, use the RMX“DOWN” program and the DOS “DPFLNK” program to transfer the poin directory to a DOS 3-1/2 inch floppy. See “Engineer Station Support Utilities” (U0-0281) for more information.




This section discusses the software configuration for the Mark V Interface. Itincludes the following sections:

• Software Configuration (Section 4-2)

• Point Record Types (Section 4-3)


4-2. Software Configuration

andfer to

eter.uld

white


4-2.1. Configuration File

The General Electric MarkV Interface is configured with a text file. Thisconfiguration file supplies all the information needed to set up communicationsto map General Electric and WDPF values and commands to each other. ReAppendix A for a sample of a configuration file.

The name of the configuration file (customized for every user) is passed to thWDPF-General Electric Mark V interface program via a command line parameFor example, if the configuration file is FPL.CFG, then the interface software cobe started at an OS/2 command prompt or in an OS/2 command file:

gsm32 FPL.CFG

4-2.2. General Information About the Configuration File

1. All text in the message map file can be in either upper or lower case.

2. Point names are case sensitive.

3. The order in which the mapping attributes for a point are specified is notimportant.

point wdpf-name = AL4, ge-name = L4

is equivalent to:

point ge-name = L4, wdpf-name = AL4

4. Commas, equals signs, spaces, tabs, and end of lines are all taken to bespace (that is, they are ignored).

point wdpf-name = BAFLR, ge-name = AFLR_CMD,gain = 256.0, bias = 0.0

is equivalent to:

point wdpf-name BAFLR ge-name AFLR_CMDgain 256.0 bias 0.0

is equivalent to:



d of

nr toan

isred

n for

n., and

pointwdpf-name = BAFLR,ge-name = AFLR_CMD,gain = 256.0,bias = 0.0

5. An asterisk (*) begins a comment. Anything between an asterisk and the enline is ignored.

6. The gain and bias are optional. If the gain and bias are not specified for aanalog point, the default values of gain = 1.0, bias = 0.0 will be used. RefeAppendixB for information on calculating gain and bias.The gain and bias cbe used on both incoming values and outgoing values.

• Incoming Values

The incoming value is converted from the specified type to a float type. It multiplied by the gain. The bias is added to the result. The final value is stoin the analog value field of the point:

point.av = ((float) invalue * gain) + bias

where

float = conversion of invalue to a floating point number invalue = 1, 2, 4 or 8 byte two's complement signed integer, or 1, 2, 4 or 8 byte unsigned integer

The use of signed or unsigned integers depends on the “signed” optiothe point.

• Outgoing Values

The analog value field of the point is read. This value is multiplied by the gaiThe bias is added to the result. This value is converted to the specified typeis put in the message to be sent.

outvalue = (INT16) ((point.av * gain) + bias)

where:

INT16 = conversion of the result to a 2 byte two's complement signedinteger


le.

4-2.3. Configuration File Parameters

Table 4-1 briefly defines the parameters in a Mark V Interface configuration fiSection 4-2.4 describes the parameters in more detail.

Table 4-1. IIU/Ethernet/Mark V Configuration File Parameters

Section Parameter Description Example Default

[hiway] Standard pointdirectory name

Filename and path pntdir = c:\wdpf\highway\pnt.dir

None

System pointdirectory name

Filename and path spdir = c:\wdpf\highway\spd.online

None

Name of themaintenance modepoint

8-char WDPF name maint-mode-point =MAINTMOD

None

The highway clock’soffset from UTC

Integer utc-offset = -240 -300

[network] Hostname of <G>node

character string g-nodename = g1 None

TCP/IP socket forcommunication

Integer socket = 768 768

[pushbutton-out]

Name of MarkVcontrol on StageLink

Two-char name controller = GA None

Start defining newpoint

point None

WDPF point name 8-char WDPF name wdpf-name =AA41BKRC

None

General Electricpoint name

20-char GeneralElectric name

ge-name =L41BKRC_CPB

None

[setpoint-out] Name of MarkVcontrol on StageLink

character string controller = GA None


point None

WDPF point name 8-char WDPF name wdpf-name = AAFLR None


[setpoint-out](cont’d)



ge-name =AFLR_CMD

None

Gain to scale output floating point value gain = 256.0 1.0

Bias to scale output floating point value bias = 0.0 0.0

Amount analog valuemust change before asetpoint command issent to Mark V

Floating point value deadband = 5.0 0.0

[event-in] Sequence of eventlogger drop number

1 - 254 soe-drop = 142 None

Name of MarkVcontrol on StageLink



point None

WDPF point name 8-char WDPF name wdpf-name = AL4 None



ge-name = L4 None

Whether changes inthe point value arelogged as sequenceof events messages inthe Historian.

yes or no soe = no Yes

[digital-in] Name of MarkVcontrol on StageLink



point None

WDPF point name 8-char WDPF name wdpf-name =AL30VLA

None



ge-name = L30V2_LO None

Table 4-1. IIU/Ethernet/Mark V Configuration File Parameters (Cont’d)




[digital-in](cont’d)

GP bit number (forsingle bits of GPpoints)

0 - 15 bit = 15 None


yes or no soe = no No

[alarm-in] Name of MarkVcontrol on StageLink



point None

WDPF point name 8-char WDPF name wdpf-name =AL33SAD1

None



ge-name =L33SAD1_ALM

None


yes or no soe = no No

[periodic] Name of MarkVcontrol on StageLink


Name of new list todefine

2-char list name list = L1 None

Period of current listin seconds

1 - 600 period = 5 None


point None

WDPF point name 8-char WDPF name wdpf-name =AL33SAD1

None





[periodic](cont’d)



ge-name =L33SAD1_ALM

None

Gain to scale analoginput

floating point value gain = 256.0 1.0

Bias to scale analoginput

floating point value bias = 0.0 0.0

GP bit number (forsingle bits of GPpoints

0 - 15 bit = 15 None

Field name to writevalue

2-char field name field = HL AV(analog)DS(digital)A2 (GP)

Whether theincoming value willbe interpreted as asigned integer

Yes or No Signed = No Yes





s:

a,

uare

his, thisy

The

en

4-2.4. Configuration File Description

The Mark V Interface configuration file is divided into the following eight sectionWDPF parameters, network parameters, and one section for each of the dataexchange functions (periodic data, digital input data, event-in data, alarm datpushbutton command data and setpoint out data).

In the following paragraphs, configuration file section names are enclosed in sqbrackets. A sample configuration file is provided inAppendix A.

Hiway Section: [hiway]

The [hiway]section specifies WDPF parameters. It must be the first section.Everything preceding it in the file is ignored. On a standard WDPF system, tsection must specify the name of the point directory. On a WEStation systemsection must specify the system point directory. Only one of the point directortypes can be specified.

A standard point directory name is specified as follows:

pntdir = xxxxxxx

where:

xxxxxxx = name of the point directory file

Any legal OS/2 filename, including a path, is valid.

A system point directory name is specified as follows:

spdir = xxxxxxx

where:

xxxxxxx = name of the system point directory file

Any legal OS/2 filename, including a path, is valid.

The offset of the WDPF Highway time relative to Universal Time Coordinated(UTC) is needed to convert the timestamps in SOE messages to highway time.offset is specified as follows:

utc-offset = xxxx

where xxxx is the offset from UTC in minutes. If the offset is not specified, th-300 is used by default.


d

dever

as ae of

S file

cket.t

The DPU failover capability can be put in maintenance mode when a specifiedigital point goes TRUE. The maintenance mode digital point is specified asfollows:

maint-mode-point = wwwwwwww

where wwwwwwww is the name of a WDPF digital point. The maintenance mois not required, and if it is not specified, the maintenance mode failures will nebe blocked.

Network Configuration Section: [network]

The [network] section specifies the parameters for network communications.

The interface communicates over a network to a <G> node. The <G> node hhost name, which must be known to the communication program. The host namthe <G> node is specified as follows:

g-nodename = xxxx

where:

xxxx = host name (refer toFigure 3-4)

The host name and the IP address of the <G> node must also be in the HOSTof the network software (PC/TCP). Refer toSection 3-3 for details about theHOSTS file. This is a required parameter.

The WDPF and General Electric systems connect to each other via a TCP soBy agreement, the socket number used is 768. If, for some reason, the sockenumber needs to be changed, a different value can be specified as follows:

socket = xxx

where:

xxx = specified socket number

Socket specification is not required and the default is 768 if the socket is notspecified.


s.

the

iontion

ed

herits

point

nte of

til

ed

herand

Pushbutton Output Section: [pushbutton-out]

A set of WDPF digital points can be mapped to Mark V pushbutton commandWithin the [pushbutton-out] section, points can be mapped to commands indifferent Mark V controls. The first thing that must be specified is the name ofcontrol. The control is specified as follows:

controller = xx

where xx is the name of the control. After the control is specified, all informatin the file applies to that control, until another control is specified or another secstarts.

After the control has been specified, points can be specified. A point is specifiusing the point keyword and specifying attributes for the point mapping. Allinformation in the file after a point keyword applies to the same point until anotpoint or control is specified or another section starts. A pushbutton point and attributes can be specified as follows:

point wdpf-name = wwwwwwww, ge-name = gggggggggg

where:

wwwwwwww = name of a WDPF digital pointgggggggggg= name of the General Electric command associated with the

Setpoint Output Section: [setpoint-out]

A set of WDPF analog points can be mapped to MarkV setpoint commands.Within the [setpoint-out] section, points can be mapped to setpoints in differeMarkV controls. The first thing that must be specified in the section is the namthe control. The control is specified as follows:

controller = xx

where:

xx = name of the control

After the control is specified, all information in the file applies to that control, unanother control is specified or another section starts.

After the control has been specified, points can be specified. A point is specifiusing the point keyword and specifying attributes for the point mapping. Allinformation in the file after a point keyword applies to the same point until anotpoint or control is specified or another section starts. A setpoint output pointits attributes can be specified as follows:



point

in

trol

til

ed

herd its

point wdpf-name = wwwwwwww, ge-name = gggggggggg,gain = xxxx, bias = yyyy, deadband = dddd

where:

wwwwwwww = name of a WDPF analog pointgggggggggg= name of the General Electric command associated with thexxxx = gain used to scale value of WDPF point before sending to Mark Vyyyy = bias used to scale value of WDPF point before sending it to MarkVdddd = deadband for the setpoint command

The order in which the attributes are specified is not important.

Event-Driven Digital Input Sections: [alarm-in], [digital-in], [event-in]

Mark V event-driven digital points can be mapped to WDPF digital points. Witheach event-driven section, points can be mapped to points in different Mark Vcontrols. The first thing that must be specified is the name of the control. The conis specified as follows:

controller= xx

where:

xx = name of the control

After the control is specified, all information in the file applies to that control, unanother control is specified or another section starts.

After the control has been specified, points can be specified. A point is specifiusing the point keyword and specifying attributes for the point mapping. Allinformation in the file after a point keyword applies to the same point until anotpoint or control is specified or another section starts. An event-driven point anattributes can be specified as follows:


where:

wwwwwwww = name of a WDPF digital pointgggggggggg = name of the General Electric event-driven point associated

with the point



be

d

t beE drop

y thee of

the

For the [digital-in] section only, a General Electric event-driven point can bemapped to a single bit of a WDPF packed group (GP) point. A bit number canspecified for the GP point as follows:

point wdpf-name = wwwwwwww, bit = xx, ge-name = gggggggg

where:

wwwwwwww = name of the WDPF GP pointxx = bit number of the GP point to write the value to (0 - 15)gggggggg = name of the General Electric event-driven digital point mappe

to the GP bit

For the [event-in] section only, one or two sequence of event logger drops musspecified. The sequence of event messages are sent to these drops. The SOnumbers can be specified as follows:

soe-drop = xxx

where:

xxx = drop number on the Westnet II Data Highway

Each point in the event-driven sections can have its changes of state logged bsequence of event (soe) logger. To define whether or not this will occur, add onthe following:

soe = yes

OR

soe = no

By default, all points in the [event-in] section have soe = yes, and all points in[alarm-in] and [digital -in] sections have soe = no.

The soe logger used is always specified in the [event-in] section.



Theified

iontion

aation

me

riod

0filens

Periodic Input Section: [periodic]

MarkV data points can be periodically sent to WDPF data points. Points fromdifferent MarkV controls can be mapped to points in the same interface unit. first thing that must be specified is the name of the control. The control is specas follows:

controller = xx

where xx is the name of the control. After the control is specified, all informatin the file applies to that control until another control is specified or another secstarts.

After the control has been specified, lists of points are defined. Each list has two-character name. The name can be any two characters, except an exclampoint (!), which is reserved for lists generated by the interface software. A list nais specified as follows:

list = cc

where:

cc is the name of the list

Each list is sent from the MarkV to the WDPF each time period. The time peis specified as follows:

period = p

where:

p is the period of the list (in seconds)

The minimum value for p is one second, and the maximum is 600 seconds (1minutes). After the list and period are specified, all the points specified in the will be put in that list, until another list or control is specified or another sectiostarts. Up to 96 points can be put in each list.



d

her

with

be

o’sy

int,

After the list is defined, points for that list can be specified. A point is specifieusing the point keyword and specifying attributes for the point mapping. Allinformation in the file after a point keyword applies to the same point until anotpoint or control is specified or another section starts. A periodic point and itsattributes can be specified as follows:


where:

wwwwwwww = name of a WDPF data pointgggggggggg = name of the General Electric data point which is associatedthe point

If the data point is an analog point, then a gain and bias for the point can alsospecified as follows:

point wdpf-name = wwwwwwww, ge-name = gggggggggg,gain = xxxx, bias = yyyy

where:

xxxx = multiplier for the value andyyyy = bias used to scale the outgoing values

For analog points, the incoming values can be interpreted as either signed twcomplement values or unsigned values. A point can be specified as signed badding:

signed = yes

to the point statement. A point can be specified as unsigned by adding:

signed = no

to the point statement. If the sign is not specified, the default is Yes.

If a General Electric logic point is being mapped to a single bit of a WDPF GP pothen a bit number can also be specified for the GP point, as follows:

point wdpf-name = wwwwwwww, bit = xx, ge-name = gggggggg

where:

wwwwwwww = name of a WDPF GP pointxx = bit number of the GP point (0 - 15)gggggggg = name of a General Electric logic point


4-3. Point Record Types

re

.

4-3. Point Record Types

The valid WDPF point record types for each section of the configuration file alisted inTable 4-2. For more information on record types, refer to “Record TypesUser’s Guide,” (U0-0131).

Table 4-2. Valid WDPF Record Types

Configuration File Section Record Types Notes

[alarm-in] DI, DL LC field must enable alarmchecking.AR field must alarm on valuesof 1. (AR = 1 or 3)See SOE notes below.

[event-in] DI, DL, DC See SOE notes below.

[digital-in] DI, DL, DC, DM, single bits ofGP

See SOE notes below.

[periodic] Any originated analog, digitalor GP

[pushbutton-out] Any originated or receiveddigital

[setpoint-out] Any originated or receivedanalog, digital or GP

Digital points can be used towrite to General Electric logiccommands. GP and analogpoints can be used to write tosetpoints and state commands

SOE NotesFor any digital point with soe =yes, the following applies:

A. The ED field is used on SOE logs.B. If the SOE logger is a WEStation HSR, do the following to set up the system correctly: - Set the EQ field for the digital SOE points in the IIU to one (1). - Configure the WEStation HSR parameter:

HSR.SOESuppressionEnable: False. (See “WEStation Historian (HSR) User’s Guide”(U0-8500) for more information.)


he

ingram

r is

Section 5. Software Startup andOperation


This section discusses the startup and operation of the IIU/Ethernet/Mark Vsoftware. It is divided into the following sections:

• Software Startup (Section 5-2)

• Software Operation (Data Exchange Functions) (Section 5-3)

• Error Reporting (Section 5-4)

5-2. Software Startup

When OS/2 (version 2.0 or later) starts, it runs the command file,STARTUP.CMDand then it runs all of the programs and command files in the Startup folder. TPC/TCP network software and the WDPF-General Electric Mark V interfacesoftware are started from the Startup folder.

During installation, theGSMSTART.CMD command file is placed in the Startupfolder. GSMSTART.CMD starts two programs, the IIU Manager, and theWDPF-General Electric Mark V interface program. The name of the point mappconfiguration file is passed to the WDPF-General Electric communication progas a command line parameter to the program.Figure 5-1 is a sample of theGSMSTART.CMD command file. In the example, the command line parametefpl.cfg.

cd c:\WDPF\HIGHWAYstart “IIU Manager” iiu_mgrcd c:\WDPF\DL\GEMKVstart “WDPF_GE Mark V” gsm32 fpl.cfg

Figure 5-1. Sample GSMSTART.CMD File


5-3. Software Operation (Data Exchange Functions)

sentin ariodn sente

hich

luesimittricctric

s inl

drrencesent toation.

sars asset

ene

ve it


5-3.1. Periodic Data from General Electric to WDPF

The WDPF system can request that values in the General Electric system beperiodically to the WDPF system. Up to 96 General Electric values can be putlist which is assigned a transmission period by the user. The minimum time peis one second., and the maximum is 600 seconds (10 minutes). Values are thefrom the General Electric system to the WDPF system once every defined timperiod. Values received by WDPF are then written into process point values ware broadcast over the WDPF highway.

These points are now available to other drops in the system. Optionally, the vacan be written to other attribute fields of the process points, such as the High Lor Low Limit fields. This allows these fields to be calculated by the General Elecsystem. Sixteen lists can be defined for each Mark V control in the General Elesystem.

If no values for a list are received for five times the period of the list, the pointthe list are set to Bad quality, and the IIU re-requests the list from the GeneraElectric system.

5-3.2. Sequence of Events (SOE) from General Electric to WDPF

Both the General Electric and WDPF systems can accurately time tag selecteevents. Messages are generated on each system to indicate the time of occuof the event. The messages generated on the General Electric system can bethe WDPF system, such that important messages are collected in a central loc

For the messages which are sent to the WDPF system, a Sequence of Eventmessage is sent over the WDPF highway, and the General Electric event appea WDPF event would on the SOE log. Also, the value of a WDPF digital point isto follow the current state of the General Electric point.

These functions can be configured for any point in any of the three event drivsections: [event-in], [alarm-in], and [digital-in]. By default, all of the points in th[event-in] section have the SOE logging enabled, and all of the other points hadisabled.

U0-1801 5-2 9/98



les.riableal

tem,en theric

neralricm the

t froms and

t. The-bit

andDPF

5-3.3. Digital Logic Events from General Electric to WDPF

Hardware I/O scan within the General Electric controls generates logic variabMessages can be sent to the WDPF system when a General Electric logic vachanges state. WDPF can put the values of the logic variables in WDPF digitpoints. These points are broadcast on the WDPF digital points. They are alsobroadcast over the WDPF highway for use in other drops. This function isconfigured in the [digital-in] section.

5-3.4. Commands from WDPF to General Electric

The General Electric system accepts two types of inputs from the WDPF syspushbutton commands and setpoint target commands. Commands are sent whWDPF point associated with the command changes state. The General Electsystem allows no more than 10 commands to be sent to it in one second.

Pushbutton

On a FALSE to TRUE transition of specified WDPF digital points, the WDPFsystem can send a message to the General Electric system, such that the GeElectric system behaves as if an operator pushed a button at a General Electconsole. Start/Stop and other pushbutton type commands can also be sent froWDPF in this manner.

Setpoint Targets

General Electric commands other than pushbutton commands can also be senWDPF. These commands include setpoint target commands, logic commandenumerated state commands. When the value of the WDPF point changes, amessage is sent to update the corresponding General Electric command poinWDPF points can be analog, digital, or packed group (GP) points. Analog or 16GP points are used to write either to setpoint commands or enumerated statecommands. Digital points are used to write to logic commands.

An analog point can be configured with a gain, bias, and deadband. The gainbias are used to scale the value sent. The deadband is the amount that the Wpoint must change before a command is sent to the Mark V.



to the

thatneralrm

toate ofnner

ownn the

l

k

rm

5-3.5. Alarms and Alarm Management

When transition in an alarm state or alarm acknowledge status occurs on theGeneral Electric system, a message is sent from the General Electric systemWDPF system. A WDPF digital point can be set to follow the alarm state of aGeneral Electric alarm, which causes a WDPF alarm to be generated when aGeneral Electric alarm is generated.

For alarms to be processed properly, the “returns to list” parameter on any dropfunctions as an Operator’s Station should be set to list alarm returns. In the GeElectric Mark V system, the alarm state is always TRUE or 1; therefore, the alastate of the WDPF points in the [alarm-in] section should be 1.

WDPF Managing General Electric Alarms

When a WDPF digital point following a General Electric alarm is alarmacknowledged, messages are sent from WDPF to the General Electric systemacknowledge, silence, or reset the General Electric alarm, depending on the stthe alarm. This allows WDPF to manage the General Electric alarms in a masimilar to its own alarm management.

Table5-1 describes what normally occurs when the WDPF system manages itsalarms, and when it manages General Electric alarms with connection betweetwo systems through the Mark V Interface.

Table 5-1. Alarm Management from WDPF to General Electric

Case No. WDPF Managing Alarms With Mark V Interface

1 WDPF digital point goes into alarmstate.

General Electric alarm which ismapped to WDPF digital point goesinto alarm state. Interface sets WDPFdigital point to same state as GeneraElectric alarm point. Point goes intoalarm.

Operator acknowledges WDPFalarm at operator’s station.

Operator acknowledges WDPFalarm at operator’s station. Interfacesends acknowledge message to MarV.

WDPF alarm leaves alarm state. General Electric alarm leaves alastate. Interface sets WDPF point tosame state.

U0-1801 5-4 9/98



statusrough

l

rm

k

Alarms from General Electric to WDPF

Table 5-2 describes what normally occurs when the General Electric systemmanages its own alarms, and when it sends alarm state or alarm acknowledgemessages to the WDPF system with connection between the two systems ththe Mark V Interface.

1(Cont’d)

Operator acknowledges WDPFalarm return at operator’s station.

Operator acknowledges WDPFalarm return at operator’s station.Interface sends request message toMark V to reset alarm from alarmqueue.

2 WDPF digital point goes into alarmstate.

General Electric alarm which ismapped to WDPF digital point goesinto alarm state. Interface sets WDPFdigital point to same state as GeneraElectric alarm point.

WDPF point leaves alarm state. General Electric alarm leaves alastate. Interface sets WDPF point tosame state.

Operator acknowledges WDPFalarm return at operator’s station.

Operator acknowledges WDPFalarm return at operator’s station.Interface sends acknowledgemessage and reset message to MarV. Alarm is acknowledged and resetfrom alarm queue.

Table 5-1. Alarm Management from WDPF to General Electric (Cont’d)

Case No. WDPF Managing Alarms With Mark V Interface


Table 5-2. Alarm Management from General Electric to WDPF

Case No.General Electric Managing

Alarms With Mark V Interface

1 General Electric point goes intoalarm state.

General Electric alarm which ismapped to WDPF digital point goesinto alarm state. Interface setsWDPF digital point to same state asGeneral Electric alarm point.

At node, operatoracknowledges General Electricalarm.

At node, operatoracknowledges General Electricalarm. Interface acknowledgesWDPF alarm.

General Electric point leaves alarmstate.

General Electric alarm leaves alarmstate. Interface sets WDPF point tosame state.

At node, operator resetsGeneral Electric alarm from alarmqueue.

At node, operator resetsGeneral Electric alarm from alarmqueue. Interface acknowledgesWDPF return.

2 General Electric digital point goesinto alarm state.

General Electric alarm which ismapped to WDPF digital point goesinto its alarm state. Interface sets theWDPF digital point to the samestate as General Electric alarmpoint.

General Electric point leaves alarmstate.

General Electric alarm leaves alarmstate. Interface sets WDPF point tosame state.

At node, operatoracknowledges General Electricalarm.

At node, operatoracknowledges General Electricalarm. Interface acknowledgesWDPF return.

At node, operator resetsGeneral Electric alarm from alarmqueue.

At node, operator resetsGeneral Electric alarm from alarmqueue. Interface does nothing.

U0-1801 5-6 9/98

5-4. Error Reporting

l, the

to aalizeis

errorsved by, it

ionsn and

for

5-3.6. Sequence of Events Timing Considerations

In order for Sequence of Event messages from two systems to be meaningfuclocks on the two systems must be very close.

In order for the clocks to have the same time, both systems must synchronizecommon clock signal. If the two systems synchronize to a common clock sign(such as IRIG-B), the clocks would be within 5 msec of each other. To synchronto an IRIG-B signal, either a clock interface unit (CIU) drop or a True Time CIUneeded on the WDPF highway. Refer to the “Clock Interface Unit User’s Guide”(U0-2101) for more information about the CIU drop. Refer to “True Time CIUUser’s Guide” (U0-2111) for more information about the True Time CIU.


When the Mark V Interface is running, it reports errors in two ways:

• Error and status messages

• Drop fault codes

5-4.1. Error and Status Messages

Error and status messages are generated by the software as normal events andoccur on the link and with the database. The 100 most recent messages are sathe program and displayed on command by the user. When the program runsdisplays a small menu. Two of the options on the menu are(v)iew to view newmessages, and(f)ile to write all accumulated messages to a file. Use these optwhen the messages are to be viewed. Error messages in setpoint, pushbuttoalarm management commands can be generated using the(c)ommand statusoption.

5-4.2. Failures and Backup Monitoring

Once the Mark V interface is running, it monitors two sets of communicationserrors:

• Communication between the IIU and the <G> node

• Communication between the <G> node and the Mark V processors in theconfiguration file

odearethe

erssorsset bytionareeen

illcur.

d in

If the <G> node fails to respond to the administrative messages, or if the <G> nreports that it cannot communicate with a Mark V processor, then the link softwsets an appropriate drop fault. If the IIU detecting the failure is in control, thenIIU fails over to its backup.

If one of the Mark V processors is being taken down for maintenance, the failovfrom failure of communication between the <G> node and the Mark V procescan be disabled by setting the maintenance mode. Maintenance mode can bespecifying a maintenance mode point in the [highway] section of the configurafile. When the specified maintenance mode digital point is TRUE, the failoversdisabled. The other failover conditions, such as a loss of communication betwthe IIU and the <G> node, will still cause the IIU to fail over. All drop faults are streported. When the maintenance mode digital point is FALSE, all failovers oc

5-4.3. Drop Fault Codes

When error conditions occur on the link or with the database, the drop is placealarm. UseTable 5-3 to interpret the drop fault codes.

Table 5-3. Drop Fault Codes

FaultCode Fault ID

FaultParameter

1

FaultParameter

2 Description Action

128 28 0 0 The IIU_MGRprogram is notrunning or the boardis not running.

Check that theiSBC386 board isrunning. Check thatIIU_MGR isrunning.

127 124 0 0 No response toadministrativemessage. Drop failsover.

Check the Ethernetand the <G> node.

127 124 1 2-char contname, e.g.,4333 = 3C

The <G> nodereports zeroconnections toindicated control.Drop fails over.

Check theStageLink. Checkthe control.

U0-1801 5-8 9/98

127 124 2 0 Connection can notbe made with <G>node. Drop failsover.

Check the Ethernetand the <G> node.

127 124 3 0 Point does not existin point directory.

View link statusmessages. Checkpoint name. Checkthat point directoryis up to date.

127 124 4 sid Indicated point doesnot exist in database.

View link statusmessages. Checkpoint name. Checkdrop database.

127 124 5 sid A pushbutton orsetpoint commandtimed out.

Command may nothave been performedin General Electricsystem. Retry thecommand.

127 124 6 sid Bad status returnedon pushbutton orsetpoint command.

View link statusmessages for badstatus returned.Consult GEDSStandard MessagesFormat (GSM)document (GEI-100165) forinterpretation.Check that GeneralElectric point is avalid command.

127 124 9 sid An alarmmanagementcommand timed out.

Command may nothave been performedin General Electricsystem. Retry thecommand.

Table 5-3. Drop Fault Codes (Cont’d)

FaultCode Fault ID

FaultParameter

1

FaultParameter

127 124 10 sid Bad status returnedon alarmmanagementcommand.

View link statusmessages for badstatus returned.ConsultGEI-100165document forinterpretation.Check that GeneralElectric point is avalid alarm.

127 124 11 sid A zero-length valuewas returned for aperiodic point.

View the link statusmessages. TheGeneral Electricpoint does not existin the <G> node.

Table 5-3. Drop Fault Codes (Cont’d)

FaultCode Fault ID

FaultParameter

1

FaultParameter


U0-1801 5-10 9/98

Appendix A. Configuration File

A-1. Section Overview

This section provides a sample configuration file which illustrates requiredconfiguration file sections and parameters.

9/98 A-1 U0-1801Westinghouse Proprietary Class 2C

A-2. Sample Configuration File

A-2. Sample Configuration File[hiway]pntdir = PNT.DIR * the name of the point directory

[network]g-nodename = gnode * name of <G> node from host tablesocket = 768 * socket number (optional)

[pushbutton-out]* this section defines pushbuttons* from WDPF to MarkVcontroller = GA

point wdpf-name = AL41BKRC, ge-name = L41BKRC_CPBpoint wdpf-name = AL41BKRT, ge-name = L41BKRT_CPBpoint wdpf-name = AL43EOSA, ge-name = L43EOST_OFFpoint wdpf-name = AL43EOSD, ge-name = L43EOST_OFOpoint wdpf-name = AL43EOSB, ge-name = L43EOST_ONOpoint wdpf-name = AL43LDRL, ge-name = L43LDRL_CPBpoint wdpf-name = AL43RESC, ge-name = L43RES_CPBpoint wdpf-name = AL70L1, ge-name = L70L_CPB

controller = GBpoint wdpf-name = BL41BKRC, ge-name = L41BKRC_CPBpoint wdpf-name = BL41BKRT, ge-name = L41BKRT_CPBpoint wdpf-name = BL43EOSA, ge-name = L43EOST_OFFpoint wdpf-name = BL43EOSD, ge-name = L43EOST_OFOpoint wdpf-name = BL43EOSB, ge-name = L43EOST_ONOpoint wdpf-name = BL43LDRL, ge-name = L43LDRL_CPBpoint wdpf-name = BL43RESC, ge-name = L43RES_CPB

[setpoint-out] * this section defines setpoints* from WDPF to MarkVcontroller = GA

point wdpf-name = AAFLR, ge-name = AFLR_CMD,gain =256.0,bias = 0.0point wdpf-name = AAPR, ge-name = APR_CMD, gain = 1.0, bias = 0.0point wdpf-name = AIPCR, ge-name = IPCR_CMD,gain = 16.0 bias = 0.0point wdpf-name = ALDR, ge-name = LDR_CMD, gain = 32.0,bias = 0.0point wdpf-name = ALIVPLR,ge-name=LIVPLR_CMD,gain =16.0,bias = 0.0point wdpf-name = ALLR, ge-name = LLR_CMD, gain =1.0, bias = 0.0

controller = GBpoint wdpf-name = BAFLR,ge-name = AFLR_CMD, gain = 256.0,bias = 0.0point wdpf-name = BAPR, ge-name = APR_CMD, gain = 1.0, bias = 0.0point wdpf-name = BIPCR, ge-name = IPCR_CMD, gain = 16.0, bias = 0.0point wdpf-name = BLDR, ge-name = LDR_CMD, gain = 32.0, bias = 0.0point wdpf-name = BLIVPLR, ge-name = LIVPLR_CMD, gain = 16.0,bias

= 0.0point wdpf-name = BLLR, ge-name = LLR_CMD, gain = 1.0, bias = 0.0

[event-in] * section for sw-scanned points

U0-1801 A-2 9/98Westinghouse Proprietary Class 2C


* sent on events from the MarkV to WDPFsoe-drop = 142controller = GA

point wdpf-name = AL4, ge-name = L4point wdpf-name = AL52GX, ge-name = L52GX, soe = yespoint wdpf-name = AL14HRA, ge-name = L14HR, soe = nopoint wdpf-name = AL14SE, ge-name = L14HMpoint wdpf-name = AL14ZSP, ge-name = L14HS

controller = GBpoint wdpf-name = BL4, ge-name = L4point wdpf-name = BL52GX, ge-name = L52GX, soe = yespoint wdpf-name = BL14HRA, ge-name = L14HR, soe = nopoint wdpf-name = BL14SE, ge-name = L14HMpoint wdpf-name = BL14ZSP, ge-name = L14HS

[digital-in] * section for digtal input points* sent on events from the MarkV to WDPFcontroller = GA

point wdpf-name = AL30VHA , ge-name = L30V2_LO, soe = yescontroller = GB

point wdpf-name = BL30VHA , ge-name = L30V2_LO, soe = yes

[alarm-in] * section for alarm points* sent on events from the MarkV to WDPFcontroller = GA

point wdpf-name = AL33SAD1, ge-name = L33SAD1_ALMpoint wdpf-name = AL33SAD2, ge-name = L33SAD2_ALMpoint wdpf-name = AL33SAD3, ge-name = L33SAD3_ALMpoint wdpf-name = AL33SRD , ge-name = L33SRD_ALMpoint wdpf-name = AL30TNHD, ge-name = L30TNH_DEV, soe = yes

controller = GBpoint wdpf-name = BL33SAD1, ge-name = L33SAD1_ALMpoint wdpf-name = BL33SAD2, ge-name = L33SAD2_ALMpoint wdpf-name = BL33SAD3, ge-name = L33SAD3_ALMpoint wdpf-name = BL33SRD , ge-name = L33SRD_ALMpoint wdpf-name = BL30TNHD, ge-name = L30TNH_DEV, soe = yes

[periodic] * section for points sent periodically from* the MarkV to WDPFcontroller = GA

list = 01 , period = 1point wdpf-name = ATNH , ge-name = TNH, gain = 0.0031point wdpf-name = ADWATT , ge-name = DWATT, gain = 0.0061point wdpf-name = ADVAR , ge-name = DVAR, gain = 0.0061point wdpf-name = ATT1SSU1, ge-name = TT_1SSU1, gain = 0.0458point wdpf-name = ATT1SBU1, ge-name = TT_1SBU1, gain = 0.0458point wdpf-name = ATTES , ge-name = TT_ES , gain = 0.0305point wdpf-name = ATTL1LS2, ge-name = TT_L1SLS, gain = 0.0122point wdpf-name = ATTTIM2 , ge-name = TT_TIM2 , gain = 0.0122point wdpf-name = ATTTAM2 , ge-name = TT_TAM2 , gain = 0.0122



point wdpf-name = ATTTIM4 , ge-name = TT_TIM4 , gain = 0.0122point wdpf-name = ATTTAM4 , ge-name = TT_TAM4 , gain = 0.0122point wdpf-name = ATTEXH2 , ge-name = TT_EXH2 , gain = 0.0092

list = 02 , period = 5point wdpf-name = ABB1X, ge-name = BB1X, gain = 0.0005point wdpf-name = ABB1Y, ge-name = BB1Y, gain = 0.0005point wdpf-name = ABB2X, ge-name = BB2X, gain = 0.0005point wdpf-name = ABB2Y, ge-name = BB2Y, gain = 0.0005point wdpf-name = ABB3X, ge-name = BB3X, gain = 0.0005point wdpf-name = ABB3Y, ge-name = BB3Y, gain = 0.0005point wdpf-name = ABB4X, ge-name = BB4X, gain = 0.0005point wdpf-name = ABB4Y, ge-name = BB4Y, gain = 0.0005point wdpf-name = ABB5X, ge-name = BB5X, gain = 0.0005point wdpf-name = ABB5Y, ge-name = BB5Y, gain = 0.0005point wdpf-name = ABB6X, ge-name = BB6X, gain = 0.0005point wdpf-name = ABB6Y, ge-name = BB6Y, gain = 0.0005point wdpf-name = AAXIAL1, ge-name = AXIAL1 , gain = 0.125point wdpf-name = AAXIAL2, ge-name = AXIAL2 , gain = 0.125point wdpf-name = AAXIAL3, ge-name = AXIAL3 , gain = 0.125point wdpf-name = ADIFFEXP, ge-name = DIFF_EXP , gain = 0.125point wdpf-name = AHYDG, ge-name = HYD_G, gain = 0.0015

controller = GB list = 01 , period = 1

point wdpf-name = BTNH , ge-name = TNH, gain = 0.0031point wdpf-name = BDWATT , ge-name = DWATT, gain = 0.0061point wdpf-name = BDVAR , ge-name = DVAR, gain = 0.0061point wdpf-name = BTT1SSU1, ge-name = TT_1SSU1, gain = 0.0458point wdpf-name = BTT1SBU1, ge-name = TT_1SBU1, gain = 0.0458point wdpf-name = BTTES , ge-name = TT_ES , gain = 0.0305point wdpf-name = BTTL1LS2, ge-name = TT_L1SLS, gain = 0.0122point wdpf-name = BTTTIM2 , ge-name = TT_TIM2 , gain = 0.0122point wdpf-name = BTTTAM2 , ge-name = TT_TAM2 , gain = 0.0122point wdpf-name = BTTTIM4 , ge-name = TT_TIM4 , gain = 0.0122point wdpf-name = BTTTAM4 , ge-name = TT_TAM4 , gain = 0.0122point wdpf-name = BTTEXH2 , ge-name = TT_EXH2 , gain = 0.0092

list = 02 , period = 5point wdpf-name = BBB1X, ge-name = BB1X, gain = 0.0005point wdpf-name = BBB1Y, ge-name = BB1Y, gain = 0.0005point wdpf-name = BBB2X, ge-name = BB2X, gain = 0.0005point wdpf-name = BBB2Y, ge-name = BB2Y, gain = 0.0005point wdpf-name = BBB3X, ge-name = BB3X, gain = 0.0005point wdpf-name = BBB3Y, ge-name = BB3Y, gain = 0.0005point wdpf-name = BBB4X, ge-name = BB4X, gain = 0.0005point wdpf-name = BBB4Y, ge-name = BB4Y, gain = 0.0005point wdpf-name = BBB5X, ge-name = BB5X, gain = 0.0005point wdpf-name = BBB5Y, ge-name = BB5Y, gain = 0.0005point wdpf-name = BBB6X, ge-name = BB6X, gain = 0.0005point wdpf-name = BBB6Y, ge-name = BB6Y, gain = 0.0005point wdpf-name = BAXIAL1, ge-name = AXIAL1 , gain = 0.125point wdpf-name = BAXIAL2, ge-name = AXIAL2 , gain = 0.125

U0-1801 A-4 9/98Westinghouse Proprietary Class 2C


point wdpf-name = BAXIAL3, ge-name = AXIAL3 , gain = 0.125point wdpf-name = BDIFFEXP, ge-name = DIFF_EXP , gain = 0.125point wdpf-name = BHYDG, ge-name = HYD_G, gain = 0.0015


V

Appendix B. Guidelines for SystemIntegration

B-1. Section Overview

This section suggests methods to use when solving some common systemintegration problems. It includes the following section:

Common Integration Problems (Section B-2)

The following topics are discussed:

• Determining in what section a GE digital point belongs.

• How to determine why setpoints and pushbuttons from WDPF to GE Markare not working and how to integrate the control systems.

• How to calculate scale gains and biases for analog periodic inputs andsetpoint-out commands.

• Enumerated state variables.

• Copying to backup.

1/98 B-1 U0-1801Westinghouse Proprietary Class 2C

B-2. Common Integration Problems

intooftionn

this

n.

d it

ion,st be

aved as

cantions


B-2.1. How to determine whether a GE digital point belongs in the[alarm-in], [event-in], or [digital-in] section of the configurationfile.

There are three types of GE event-driven digital points that can be transferredthe WDPF system: alarm, SOE, and digital inputs. In order for these types points to work, they must be put into the corresponding section of the configurafile: [alarm-in], [event-in], and [digital-in]. If a point is in the wrong section, thethe values will not be transferred correctly.

For each control on the GE system, there are three configuration files of note onsubject: ALARM.LST, EVENT_Q.SRC, and UNITDATA.DAT.

If a GE point is listed in ALARM.LST, then it can be put into the [alarm-in] sectio

If a GE point is listed in EVENT_Q.SRC, then it can be put into the [event-in]section.

To check whether or not a point can be put into the [digital-in] section, first finin UNITDATA.DAT. The point type for the point must be 1 (logic point) and thescale type must be either 0 (contact input) or 1 (inverted contact input). In additfor each contact used in the [digital-in] section, the change cell detect mask muenabled. Refer to GEH-6195, Rev. B, Appendix B, Section B-3, for moreinformation.

Logic variables on the GE side which do not specifically fit any of the abovequalifications can be used in the [periodic] section. In other words, points that ha state of 0 or 1 on the GE side, but which are not I/O points, can be configureperiodic points.

GE points may exist in more than one of these configuration file sections. Theybe put in more than one section depending on whether the functions of the secare desired.

U0-1801 B-2 1/98Westinghouse Proprietary Class 2C


In

his

the

the

fromutted,en

E toed

ay

PF.

log

B-2.2. How to determine why setpoints and pushbuttons from WDPF toGE Mark V are not working and how to integrate the controlsystems.

The GE system has various modes for accepting commands over the link. general, commands will either be accepted or rejected. If the GE system isrejecting commands, then the WDPF DPU logic must be set up to handle tsituation for the control to work smoothly. This may involve logicprogramming on both the WDPF and GE systems.

For the situation where setpoints are being sent to the GE system, if the GEcontrol is rejecting the WDPF setpoint commands, then the actual setpoint inGE system and the setpoint being sent by the WDPF system may bedifferent.When the WDPF setpoint commands are then accepted, a bump incontrol occurs.

Two solutions to this problem are suggested here.

Solution 1

Do not use the setpoint-out command. If GE setpoints need to be changedthe WDPF system, use RAISE/LOWER digital signals with pushbutton-ocommands. In this situation, if the RAISE/LOWER signals are rejecthe actual GE setpoint will not move, but there will be no mismatch betwethe two systems.

Keep in mind that the pushbutton-out commands only get sent on a FALSTRUE transition of the WDPF digital point, so a continuous raise would neto pulse the RAISE WDPF digital point.

The advantage to this solution is low communications overhead.

The disadvantages to this solution are:

• RAISE/LOWER bits may not be available on the GE control logic, and mtherefore need to be created.

• Logic to create pulsing action on digital signals must be created on WD

• Each setpoint requires two digital points in each system, plus one anapoint to read back the actual setpoint.



ointare

Solution 2

Create a ‘mode’ digital point in the GE system, and have the WDPF setptrack the GE setpoint if the mode digital indicates that the WDPF commandsbeing rejected.

Example

The following is an example using Solution 2.TableB-1 describes the points usedin the sample interface configuration file.

Sample Interface Configuration File

in [setpoint-out] section

point wdpf-name = SPCMD, ge-name = SP_CMD, gain = xx

in [periodic] section:

point wdpf-name = SPACT, ge-name = SP_CMD, gain = yy

in [digital-in] section:

point wdpf-name = DCSDIASB,ge-name=LOOP_DCS_DISABLE

Table B-1. Sample Interface Configuration File Points

Point Description

GE Points

LOOP_DCS_DISABLE TRUE if WDPF commands are rejected; FALSE if WDPF

commands are accepted

SP_CMD Holds the setpoint in the GE system

WDPF Points

SPCMD Computed setpoint to send to GE system

SPACT Reads actual GE system setpoint (SP_CMD). If WDPF

commands are enabled, this point should have same

value as SPCMD.

DCSDISAB Reads the loop control mode point

(LOOP_DCS_DISABLE)



d,

lues

DPU Control:

Explanation:

If LOOP_DCS_DISABLE indicates that WDPF commands are being acceptethen the XTRANSF in the loop passes the output of the XMA (or whateveralgorithms compute the setpoint) to SPCMD. SPCMD writes the computed vato the GE system.

XMA

p

XTRANSF flag = DCSDISAB

SPACT

TRUE

SPCMD

FALSE

(= SPACT if DCSDISAB is TRUE)

c


hene of

GEGE

ned

hm.

eard

If LOOP_DCS_DISABLE indicates that WDPF commands are being rejected, tthe XTRANSF in the loop passes the value of SPACT, (which is the actual valuthe GE setpoint) to SPCMD. The XMA (or whatever algorithms compute thesetpoint) track the value of SPACT. SPCMD writes the value of SPACT to thesystem. The value will be rejected, but since it is the same as the setpoint in thesystem, there is no mismatch between the systems.

The advantages of this solution are:

• It allows setpoints to be transferred smoothly. Many loops could be turon/off with one GE digital mode point, but each loop could have its ownmode point if needed.

The disadvantages of this solution are:

• The mode point may need to be created if it is not available in the GEsystem.

• Each setpoint requires three WDPF points, two GE points and anXTRANSF in a graphic loop.

• This method only works if the setpoint is computed in a graphic algorit

B-2.3. How to calculate scale gains and biases for analog periodicinputs and setpoint-out commands.

Open the UNITDATA.DAT and SCLEDATA.DAT configuration files. These arconfiguration files in the GE Mark V control system. They can be found on the hdisk of either the node or the <G> node. The GE project manager will befamiliar with these files.

For each point, do the following:

1. Find the point in UNITDATA.DAT. Each line in this file looks like this:

TNH 4634 002 0068 0000 0000 0001 0060 1434TNH_RPM 6025 002 0088 0000 0000 0001 0060 1F12

where:

TNH = GE point name4634 = point number (not needed here)002 = point type (002 is analog - two-byte integer)0068 = scale code type (important for this)

2. Get the scale code type from the line. This is 68 for TNH.


e
3. Find the scale code type in SCLEDATA.DAT. Each line in this file looks likthis:
#scale_data 68 128.000000 0.000000 2 % PCT#scale_data 88 8192.000000 0.000000 0 rpm RPM

where:

68 = scale code type (important for this)128.0 = full scale value of the point (max)0.000 = zero scale value of the point (zero)

4. Compute the gain and bias from the max and zero.

For analog inputs (in the [periodic] section):

bias = zerogain = (max - zero)/fullscale

For the example of TNH as an input:

fullscale = 32767max = 128.0zero = 0.0

Therefore,

bias = 0.0gain = (128 - 0)/32767 = .0039064

For the example of TNH_RPM as an input:


Therefore,

bias = 0.0gain = (8192 - 0)/32767 = .25



.ple,

ato

.tate

dic]ts.

For analog outputs (in the [setpoint-out] section):

bias = fullscale * zero/(zero - max)gain = fullscale/(max - zero)

For the example of TNH as a setpoint output:


Therefore,

bias = 0.0gain = (32767)/(128.0 - 0.0) = 256.0

For the example of TNH_RPM as a setpoint output:


Therefore,

bias = 0.0gain = 32767/(8192.0 - 0.0) = 4.0

B-2.4. Enumerated State Variables

Certain points on the GE side are categorized as enumerated state variablesEnumerated state variables have multiple states for a given condition. For examthe fuel type might be GAS, MIXED, or OIL, where GAS would correspond tovalue of 0 for fuel type, MIXED would be equal to a 1, and OIL would be equala 2. The ASCII text string which corresponds to the specific enumerated statevariables can be found in the GE Mark V system as the file “ENUMDATA.DATThis file is necessary to the WDPF graphics programmer if any enumerated svariables are to be displayed on the WDPF side.

Enumerated state variables are integer type and can be received in the [periosection for display purposes. The values can be read into analog or GP poin



t theead bym

andory

B-2.5. Copying to Backup

When copying the primary DPU control and logic to the backup, the database abackup is taken off-line. Because of this, the Mark V Interface software cannot rand write the database. This software in the backup DPU should be stoppedpressing(q)uit from the program’s menu. After the copy is complete, the progracan be restarted.

The process of copying to backup does not copy any files between the primarythe backup IIU. If any changes are made to the configuration file or point directon the primary, the backup must be updated by hand.


Index

-

Aalarm data 5-4alarm management 5-4alarm-in 4-11

See also configuration file.

Ccable connections

fully redundant system 2-3non-redundant system 2-9redundant system with non-redundant node

and General Electric cable 2-7redundant system with non-redundant

General Electric cable 2-5CMOS parameters 3-6commands 5-3CONFIG 3-12configuration file 4-2, 4-4, 4-8, 4-10, 4-11, 4-

14, B-2, B-4parameters 4-4See also Appendix A.

Ddata

alarm 5-4commands 5-3digital logic events 5-3periodic 5-2SOE 5-2

data exchange 1-1, 5-2diagram 1-2

digital logic events 5-3digital-in 4-11

See also configuration file 4-12DPU 1-1, 2-1, 2-2, 2-3, 2-5, 2-7, 2-9drop faults 5-8

Eenumerated state commands 5-3error messages 5-7, 5-8

See also drop faults 5-7Ethernet 1-1, 2-1, 3-8event-i 4-11event-in


GGSM messages 1-1

GSMSTART.CMD file 3-13, 5-1guidelines

system integration B-1

Hhard disk

parameters 3-7hardware

configuration 2-2General Electric 2-2WDPF 2-1

hiway 4-8See also configuration file.

HOSTS file 3-9, 3-10, 4-9

IIIU 1-1, 2-9

partner 2-2, 2-3, 2-5, 2-7primary 2-2, 2-3, 2-5, 2-7

installationhardware 2-1software 3-1

IP protocol 3-8iSBC272 VGA Adapter Jumper 3-4iSBC386sx Multibus card 2-1, 2-3, 2-5, 3-1, 3

5

Llogic commands 5-3

MMark V Interface 1-1monitoring the interface 5-7Multibus card 1-1

Nnetwork 4-9

See also configuration file 4-9nodes

C 2-2D 2-2G 2-2

non-redundant system 2-9

OOS/2 3-1, 3-8

P

1/98 Index-1 U0-1801Westinghouse Proprietary Class 2C

Index

PC/TCPnetwork software 3-10

periodic data 5-2point record types 4-15protocol

application 1-1network 1-1

Pushbutton command 5-3pushbutton-out 4-10


Rrecord types used 4-15redundant configuration 2-2, 2-5, 2-10

full redundancy 2-3, 2-4, 2-6non-redundant communication system 2-9redundant system with non-redundant node

and GE Stagelink cable 2-8reference documents 1-4

SSequence of Events (SOE) data 5-2setpoint target commands 5-3setpoint-out 4-10

See also configuration file 4-10SOE time tags 5-2, 5-7software

configuration 4-1installation 3-1operation 5-1startup 5-1

software configuration 4-1spd.online file 3-13Stagelink 2-5, 2-7, 2-9startup 5-1status messages 5-7system integration B-1

TTCP/IP protocol 1-1

U0-1801 Index-2 1/98Westinghouse Proprietary Class 2C