EGD Mark VIe Integration Procedure

BENTLY NEVADA No.
179842 Rev A Page 1 of 69

Code ID no.: Name: J. Robert
Procedure 20230
3500/91 EGD Module Mark VIe Integration Procedure Approved: J. Robert
Revision Name Approved Description
A J.Robert J.Robert Saved File Change
Contents
1. Purpose ......................................................................................................................................... 3
2. Scope............................................................................................................................................. 3
3. Reference ...................................................................................................................................... 3
4. Requirements................................................................................................................................ 4
5. Verification ................................................................................................................................ 5
6. Warnings.................................................................................................................................... 5
6.1 Mark VIe Control System ......................................................................................................... 5
6.2 Bently Nevada 3500 Monitoring and Diagnostic System .......................................................... 6
7. Software Backups ..................................................................................................................... 6

7.1 Mark VIe Control System HMI ................................................................................................. 6
7.2 Bently Nevada 3500 Monitoring and Diagnostic System .......................................................... 7
8. Item(s) Not Covered .................................................................................................................. 7
9. Mark VIe – TMR or Dual Configuration - Consumed EGD Limitation..................................... 8
10. Mark VIe – SIMPLEX Configuration - Consumed EGD Limitation.......................................... 8
11. 3500 Group Action Commands ................................................................................................ 9
12. Adding a 3500 Rack as a External Device ............................................................................... 9
13. 3500/91 Produced EGD Page.................................................................................................. 14

13.1 New 3500 External Device Produced EGD Page Configuration ......................................... 17
13.2 Manual 3500/91 Module Produced EGD Page Configuration............................................. 17
13.3 .CSV File 3500/91 Module Produced EGD Page Configuration.......................................... 17
14. 3500 Rack Configuration ........................................................................................................ 18

14.1 Configuring the 3500/91 EGD Module:............................................................................... 18
14.2 Direct Connection - RS232................................................................................................. 18
14.3 Using the Rack Configuration Software.............................................................................. 19
14.4 3500/91 EGD Module Basic Device Configuration ............................................................. 20
14.5 3500/91 Produced EGD Exchange Configuration............................................................... 21
14.6 Assigning Points to the 3500/91 EGD Produced Exchange(s)............................................ 22
14.7 Exporting the 3500 Report File........................................................................................... 27
14.8 3500/91 Module EGD Report Configuration ....................................................................... 29
3500/91 EGD Module Mark VIe No. 179842 Rev A Page 2 of 69
Integration Procedure
15. Control System HMI Configuration ........................................................................................ 34

15.1 Host File............................................................................................................................. 34
15.2 CONFIG.DAT..................................................................................................................... 34
16. Using the 3500/91 EGD Data/Tags in the Control System Code .......................................... 35
16.1 3500/91 EGD Data/Tags Health Verification ...................................................................... 43
16.2 VAR_HEALTH Block – ....................................................................................................... 51
16.3 Consumed EGD Exchange Health Status .......................................................................... 52
16.4 HMI Configuration – Referenced Devices – CIMPLICITY Project Points ............................ 52
16.5 CIMPLICITY Project Points................................................................................................ 57
16.6 Adding Tags to the 3500 External Device Produced EGD Page......................................... 60
16.7 Updating the HMI Referenced Device ................................................................................ 61
17. Troubleshooting...................................................................................................................... 66
1. Purpose
To establish a basic procedure to integrate a Bently Nevada 3500/91 EGD Communication
Gateway module to a Mark VIe control system.
2. Scope
This document attempts to cover as much general information on these configurations for
each of products and their associated software packages.
There are no universal HMI screens, 3500 Rack configurations, Mark VIe application code,
and or signal/tag lists for a standard integrated system. Each system must be developed
based on the customer requirements.
The integration of the 3500/91 Communication Gateway Module to the Mark VIe control
system allows for the 3500 Produced EGD static data/tags to be used to populate a control
system HMI operator interface computer screen, trend the 3500/91 Produced EGD static
data/tags using the Mark VIe trender functionality, and store the 3500/91 Produced EGD
data/tags to the GE PI Based Historian computer.
In most cases the 3500 system and the control Mark VIe system for the same customer will
be engineered at different times. Therefore if at all possible the project, sales, and or
requisition engineers for each product should make every effort to at least provide
information consisting of data/tags, exchange points in some form (Excel .xls spreadsheet
preferred) so that the engineers who have to configure the systems have some idea of what
data/tags from the opposite system they will need to configure on their particular system.
If the customer has a 3500 system with a 3500/91 EGD module, and a Mark VIe control
system already on-site and the customer wishes to integrate the 3500 system with a
3500/91 EGD module to a Mark VIe control system. In this application it would be the
responsibility of the field engineer to configure the 3500 system and the Mark VIe control
system devices at the customer site.
One or more Mark VIe turbine controllers could consume the 3500/91 produced EGD
data/tags. The controller(s) could take action based on the data received from the 3500/91
EGD module, however the action should not include control system GE turbine unit trip
command functionality.
3. Reference
Bently Nevada Documentation
179839 3500/91 EGD Module Application Guideline
161232 3500/91 EGD Comm Gateway Module User's Guide
129777 3500 Rack Configuration and Utilities Guide
167060 3500/91 EGD Gateway Protocol Configuration Manual
129766 3500 Monitoring System Rack Installation & Maintenance Manual
GE Control System Documentation

GEH-6700B ToolboxST Guide for Mark VIee Control
GEH-6706A ToolboxST Guide for WorkstationST
4. Requirements
In order to use a 3500/91 EGD module a 3500/22 TDI module is required in the 3500 rack.
A project proposal that includes a 3500/91 EGD Communication Gateway module to a GE
turbine Mark VIe control system should be jointly reviewed between Bently Nevada and
Global Control Services project personnel. A certain amount of integration work such as
mapping of 3500/91 EGD tags will need to be done for each job, which requires preparation.
This document only includes Mark VIe systems that utilize the WorkstationST software. This
document does not include configuration for Mark VIe systems using the TCI software
application or use a control system SDB.
The standard configuration of the 3500 system is having one (1) 3500 Rack per GE turbine
unit. The single 3500 Rack can have two (2) 3500/91 EGD modules that can provide
redundant produced EGD exchange data.
The user has a working technical knowledge of the following products and software:
Mark VIe turbine controller, GE Control System Toolbox software, EGD communication,
TCP/IP communications, Bently Nevada 3500 Rack configuration software, 3500 /91 EGD
Communication Gateway module, and GE Fanuc CIMPLICITY.
The instructions in this document assume that the user will be using the HMI operator
interface computer to connect to the 3500 Rack via a direct connection to the RS232
connector on the front panel of the 3500/22 Transient Data Interface module located in Slot
1 of the 3500 Rack and that the 3500 Rack Configuration software is loaded onto the HMI
operator interface computer.
If the user is accessing the 3500 Rack from another computer then certain configuration
information will need to be transferred to the HMI operator interface computer in order to
configure the new 3500 external device EGD Produced Page.
Additional information on connecting to the 3500 Rack, uploading the Rack configuration,
and accessing the Rack modules can be found in the 3500 Rack Configuration and Utilities
Guide 129777 Rev-B.
The instructions in this document pertain to the software versions listed. Changes to later
revisions of the software listed may impact the instructions of this document.
ToolboxST
Release 1
Version V03.00.28C Build 3
Rack Configuration Software

Version: 3.90.0313
HMI Computer
Operating System: Microsoft Windows XP Professional Service Pack: 2
Version: 5.1 - Build: 2600.xpsp_sp2_gdr.050301-1519
CIMPLICITY:
Version: 6.10 Build 5538 SP 4
Microsoft Excell 2000
Version: 9.0.8961 SP-3
5. Verification
Verify that the 3500 Rack has a 3500/91 EGD Communication Gateway module.
Verify that the 3500/91 EGD communication module is connected to the control system Unit
Data Highway UDH Ethernet network. In the rear of the 3500/91 EGD module there should
be an I/O module with a single RJ45 10/100 Ethernet port. Standard CAT5 Ethernet cable
should be used to connect from this RJ45 10/100 Ethernet port to the closest Mark VIe
control system Unit Data Highway UDH Ethernet switch.
6. Warnings
6.1 Mark VIe Control System
The configuration work performed in this document will result in Mark VIe control system
application code changes.
These application code changes could result in a Major Difference between the Mark VIe
control system application code loaded in the toolbox software and that loaded into the
actual Mark VIe turbine unit controller.
In order for the Major Difference between the toolbox application code and the application
code in the
Mark VIe turbine controller to be equalized the Mark VIe turbine controller will need to be
stopped and then restarted.
IMPORTANT
• Stopping and starting a Mark VIe turbine controller should never be performed on a
running turbine unit.
• Stopping and then restarting a controller during unit operation can result in serious
system instability, which could result in system failure and possible damage to the
turbine unit and other equipment.
• Even with the Mark VIe turbine unit /system down – off-line- not running – in outage -
extreme caution should be followed when performing a manual stop and restart of a
Mark VIe controller. Any and all customer as well as GE site safety procedures and
processes should be followed.
6.2 Bently Nevada 3500 Monitoring and Diagnostic System

The configuration work performed in this document will change one or more modules in the
Bently Nevada 3500 Rack. The selected module(s) will be taken off line during the
download of the new module(s) configuration.
IMPORTANT
• The configuration change and subsequent download will result in a loss of machinery
data and could change the state of any relays with in the 3500 Rack.
• Even with the Mark VIe turbine unit /system down – off-line- not running – in outage -
extreme caution should be followed when performing a change to the Bently Nevada
3500 Rack. Any and all customer as well as GE site safety procedures and
processes should be followed.
7. Software Backups
It is recommended that prior to making changes to the Mark VIe HMI computer and it’s
associated control system files that a back up of the HMI computer is made. A back up of
the 3500 Rack system files should also be made. Below is a listing of each system and the
files and locations that should be included in the back up.
7.1 Mark VIe Control System HMI
File Type File Location

HOST C:\ WINDOWS\system32\drivers\ etc
Master E:\Master
Site E:\Site
7.2 Bently Nevada 3500 Monitoring and Diagnostic System
3500 System Configuration (.rak)

Once you are connected to the 3500 Rack you will have to Up-load the configuration from
the 3500 Rack. From the File menu select Upload from Rack
Once the Upload is completed you should save that the configuration (Save As)
8. Item(s) Not Covered
The creation of a CIMPLICITY HMI screen to display 3500 signals data/tags is not covered.
The configuration of the GE PI Based Historian computer to record 3500 signals data/tags is
not covered.
The configuration / creation of Mark VIe turbine control code utilizing 3500 signals data/tags
is not covered.
The configuration of the Mark VIe trender functionality to trend 3500 signals data/tags is not
covered.
The configuration of the 3500 group action commands from the produced EGD exchange of
the Mark VIe control system is not covered.
9. Mark VIe – TMR or Dual Configuration - Consumed EGD Limitation
On a single GE turbine unit with a Mark VIe in TMR or Dual configuration there is a limitation
of 1,380 bytes of consumed EGD data that can be communicated over the control system
I/O NET. Reference: Mark VIe - GEH-6421K_Vol_I Chapter 3 Networks 3–7 through 3-
12.
The I/O NET consumed EGD limitation for TMR and Dual Mark VIe is 1,380 bytes. This
means if a 3500/91 EGD module is used on a single GE turbine unit with a Mark VIe in TMR
or Dual configuration the total number of byte EGD data that that the 3500/91 module can
produce will be dependant on the level of consumed EGD data for that particular units Mark
VIe in TMR or Dual configuration.
Keeping in mind that a Mark VIe could be consuming EGD data from other devices such as
EX2100, LCI, and DCS systems.
As an example: A single GE Gas turbine unit with a Mark VIe TMR configuration. If the
Mark VIe for the single gas unit is consuming EGD data from only one external EGD device
and that one external EGD device is a single 3500/91 EGD module. Then that single
3500/91 EGD module is limited to producing a total of 1,380 bytes of data.
If the 3500 system for that single GE gas turbine unit had two redundant 3500/91 EGD
modules then the combined produced EGD data from both 3500/91 EGD modules would
still have to be under the 1,380-byte limitation.
10. Mark VIe – SIMPLEX Configuration - Consumed EGD Limitation

It is recommended that the total produced EGD data from a single 3500/91 EGD module for
a single GE turbine unit be limited to a total of 5,520 bytes. This total byte limitation
translates into a single 3500/91 EGD module using all four of its available produced EGD
exchanges with each of these exchanges having a total of 1,380 bytes per exchange.
If the 3500 system for that single GE turbine unit had two redundant 3500/91 EGD modules
then the combined produced EGD data from both 3500/91 EGD modules would still have to
be under the 5,520 -byte limitation.
Below is a segment from a single 3500.91 EGD exchange . Each 3500/91 EGD Exchange
can provide for 1,400 bytes of data. It is recommended that when configuring the 3500.91
EGD module that you do not exceed 1380 bytes of data per 3500/91 EGD exchange
11. 3500 Group Action Commands

Group Action Commands are specialized features that require expert understanding of their
functionality.
Group Action Commands should only be implemented on certain GE turbine units under
specific controlled instances.
The Group Action Commands are the only consumed EGD exchange available on the
3500/91 EGD module. This consumed EGD exchange should remain in the inactive
condition (un-checked).
Strongly advise consulting Bently engineering prior to implementation of this feature on any
application.
Additional Group Action Command Warnings:
Group Action Commands are to be only initiated during turbine unit startup and or during
maintenance. GE turbine Mark VIe / Mark VIee control application code should include
functionality that prevents the initiation by the control system of the Group Action
Commands during normal turbine operation.
The Group Action Command addressing in the 3500/91 EGD module is fixed. If the GE
turbine Mark VIe / Mark VIee control system produced EGD exchange containing the group
action commands is compressed then there will be a signal address difference between the
control system Group Action Command signals and the 3500/91 EGD module Group Action
Command signals. Under this circumstance errors in Group Action Command functionality
will occur.
Group Action Commands are valid in 3500 rack systems that have only one 3500/91 EGD
module.
12. Adding a 3500 Rack as a External Device
The addition of the new 3500 external device should be done on the file server HMI operator interface
computer. This HMI should contain the Master directory/folder. Reference: GEH-6706A Chapter 7 – Editor for
External Devices
1. From the ToolboxST System Editor Tree View right click and add a new External Device.
2. In the dialog box that appears after you select External Device you should provide a unique name to
the new External Device. In this example we are adding one (1) Bently Nevada 3500 Rack. The name
must begin with a letter and no spaces are allowed.
NOTE:
• Multiple 3500 Racks should be separated by the naming convention: R1, R2, R3 etc…
• If the 3500 Rack has two /91 modules (for redundant communication) the Primary /91 module
would be identified as BN3500R1 and the Secondary /91 module would be identified as
BN3500R1a
Examples:
BN3500R1 = A 3500 Rack with one (Primary) 3500/91 EGD module.
BN3500R1a = A 3500 Rack with one (Secondary/Redundant) 3500/91 EGD module.
BN3500R2 = A second 3500 Rack with one (Primary) 3500/91 EGD module.
BN3500R2a = A second 3500 Rack with one (Secondary/Redundant) 3500/91 EGD module.
3. Select Finish once you have entered the name of the 3500 external device.
Once the new 3500 device has been entered and named configure the following.
The Tree View should now contain the new 3500 Rack device.
In the Property Editor: Main – App and Doc Path blank (standard).
Operational section:
Enable EGD Editor: True
Enable Get From SDB False
Leave Slashes: False
Start Directory: Blank
Switches: Blank
The Summary View shows the new 3500 Rack connected to the Unit Data Highway (UDH).
4. Double click on the new 3500 Rack in the Summary View area. This will bring up a Please
Waite Loading component dialog box.
5. Two Tabs will appear. In the General tab select – Network Adapter 0 -.
In the Adapter settings you must provide a Host Name and specify the Unit Data Highway UDH
IP Address of the new 3500 Rack device. The Host Name should be the same as the name given to
the new 3500 external device.
The control system Boiler Plate Host file version 7.0 lists IP Addresses 192.168.101.74 –
192.168.101.88 as “Reserved for Bently - Future use “. Based on this information, in this example we
will use the .74 IP address, however it would be best to check the HOST file in the control system HMI
operator interface computer on your particular system to determine the available UDH IP address to
meet your systems specific requirements.
Wire Speed should be kept at default setting of Auto. In the Network settings: Network Name
should be kept to default UDH and Subnet Mask default 255.255.255.0
13. 3500/91 Produced EGD Page

With the Bently Nevada 3500 system now added as a device on the control system the Produced EGD page
of the Bently Nevada 3500/91 module must now be configured in the control system Toolbox ST software.
1. Select the EGD tab. Left mouse click on Produced Pages. Select Add Page.
Enter Page Name in dialog box and then select OK
NOTE:
• A single 3500/91 EGD module has the ability to provide four (4) Produced EGD pages. Multiple pages
should follow a simple numerical incrimination: _PG2, _PG3 etc..
• Multiple 3500 Racks should be separated by the naming convention: R1, R2, R3 etc…
• If the 3500 Rack has two /91 modules (for redundant communication) the Primary /91 module
would be identified as BN3500R1 and the Secondary /91 module would be identified as
BN3500R1a
Examples:
BN3500R1_PG1 = EGD Page 1 of the 1st 3500 Rack with one (Primary) 3500/91 module.
BN3500R1a_PG1 = EGD Page 1 of the 1st 3500 Rack with one (Secondary) 3500/91 module.
BN3500R1_PG2 = EGD Page 2 of the 1st 3500 Rack with one (Primary) 3500/91 EGD module
BN3500R1a_PG2 = EGD Page 2 of the 1st 3500 Rack with one (Secondary) 3500/91 module.
BN3500R2_PG1 = EGD Page 1 of the 2nd Second 3500 Rack with one (Primary) 3500/91 module.
BN3500R2a_PG1 = EGD Page 1 of the 2nd 3500 Rack with one (Secondary) 3500/91 module.
BN3500R2_PG2 = EGD Page 2 of the 2nd 3500 Rack with one (Primary) 3500/91 EGD module
BN3500R2a_PG2 = EGD Page 2 of the 2nd 3500 Rack with one (Secondary) 3500/91 module.
2. Configure the following once the new EDG page is created.
Destination:
Ethernet 0 True
Mode Broadcast
Misc:
Exchanges 0 default
Setup:
Allow Editing True
Name BN3500R1_PG1
Period 1000
Skew 0
3. On the newly created Produced Page for the 3500 Rack organize the data column by placing the
mouse on the upper left corner block and right clicking. Select Organize Columns.
4. Manipulate the column selections so that the type and placement of each column should be as is
shown in the below dialog box.
When done click OK

5. The final new 3500 external device EGD Produced Page should look like below:
It is assumed at this point that no data/tags have been configured from the 3500 Rack - 3500/91
module therefore you will need to minimize this page until the 3500 data/tags have been configured on
the 3500/91 EGD module – following the steps outlined below.
You can not perform a Bind Consumed , build Procedure at this point will result in an error since no
EGD points have been entered for the new EGD Page
13.1 New 3500 External Device Produced EGD Page Configuration
With the new 3500 device and it’s associated Produced EGD Page created the information for each of the
3500 tags on the EGD Produced Page will now have to be entered.
The information for each 3500 tag/signal can be entered into the EGD Produced Page manually (one
at a time) or using Microsoft Excel and .CSV files.
13.2 Manual 3500/91 Module Produced EGD Page Configuration
One could enter each 3500/91 module EGD data/tag into the new 3500 external device EGD Produced Page
(shown above), however you would need to know all of the information from each 3500 tag to match each of
the columns created in the new 3500 external device EGD Produced Page (as shown above).
If you have the 3500/91 module configured as well as all of the associated 3500 EGD data/tags Exchange
Points skip to Step 3 Page 15 – Assigning Points to the EGD Produced Exhange followed by Steap 1-6 Page 19
3500/91 Module EGD Report Configuration.
13.3 .CSV File 3500/91 Module Produced EGD Page Configuration
Their is no automated process for exporting the data/tags directly from the 3500/91 module into the
new 3500 external device EGD Produced Page created in Workstation ST.
The process of exporting the 3500 data/tags from the Bently Nevada 3500/91 module to the new 3500
external device EGD Produced Page created in Workstation ST becomes a matter of configuring, cutting, and
pasting .CSV files and then importing the data/tags from the 3500/91 module to the new 3500 external
device EGD Produced Page created in Workstation ST.
In order to use the .CVS export/import method Microsoft Excel would need to be loaded on the HMI
computer used to add the new 3500 device and it’s associated Produced EGD Page.
14. 3500 Rack Configuration
14.1 Configuring the 3500/91 EGD Module:
Before you can import the 3500 data/tags into the Mark VIe new 3500 device and associated Produced EGD
Exchange you will have to configure the 3500/91 EGD Communication Gateway module itself as well as
configure each Produced EGD page you want to use with the 3500 data/tags.
The following assumes that the 3500 Rack is already configured (minus the 3500/91 module), the user has
the 3500 Rack Configuration software available, and the user can connect to the 3500 Rack.
There are two standard ways of connecting to a 3500 rack:
• A direct connection to the RS232 connector on the front panel of the 3500/22 Transient Data
Interface module located in Slot 1 of the 3500 Rack.
• Ethernet connection to the 3500/22 TDI module.
A control system HMI operator interface computer can ONLY be used to configure the Bently Nevada
3500/91 EGD module using the RS232 connection method.
The 3500/22 TDI Ethernet network should NEVER be incorporated into a GE control system Ethernet Unit
Data Highway (UDH) and or the Plant data Highway (PDH).
14.2 Direct Connection - RS232

Connect the computer directly to the rack by using an RS232 cable as shown in the following figure.
14.3 Using the Rack Configuration Software

1. Open the 3500 System Configuration Utility:
Start | Programs | 3500 Software | Rack Configuration Software
Load the .rak file for the 3500 system. From the System Configuration Utility Select File – Open – The default
location for the .rak file is – C:\3500\Trains\Primcfg Once the .rak file is loaded connect to the 3500 Rack:
2. Once connected to the 3500 Rack right mouse click on the 3500/91 module and select Options
14.4 3500/91 EGD Module Basic Device Configuration

The following covers the basic device configuration for the 3500/91 EGD module. The control system Boiler
Plate Host file version 7.0 lists IP Addresses 192.168.101.74 – 192.168.101.88 as “Reserved for Bently - Future
use “. Based on this information, in this example we will use the .74 IP address, however it would be best to
check the HOST file in the control system HMI operator interface computer on your particular system to
determine the available UDH IP address to meet your systems specific requirements.
If the single 3500 Rack is to support Dual 3500/91 EGD modules for redundancy then the second 3500/91
EGD module Source IP address should follow the primary 3500/91 EGD module.
In this example our 3500 Rack contains only one 3500/91 EGD module and we have selected a Source IP
address of 192.168.101.74.
If we were to add a second (redundant) 3500/91 EGD module to this 3500 Rack we would use a Source IP
address (assuming it is available) of 192.168.101.75. The remaining network configuration settings for the
second (redundant) 3500/91 EGD module would follow what was used on the primary 3500/91 EGD module.
Source IP: 192.168.101.74

Destination IP: 192.168.101.255 (default)
Subnet Mask: 255.255.255.0 (default)
Broadcast: Selected (default)
Use Source IP: Selected (default)
Note:
In later steps you will need to download the new configuration to the 3500/91 EGD module.
If the single 3500 Rack contains two 3500/91 EGD modules then it is best to download them one at a time.
14.5 3500/91 Produced EGD Exchange Configuration

The /91 EGD module provides four (4) produced EGD exchanges. They are labeled Produce 1, Produce 2,
Produce 3, and Produce 4. The following covers the basic configuration for each of the 3500/91 Produced
EGD exchanges.
The initial values of the Configuration Signature of a particular /91 Produced EGD exchange will be Major
Number = 0 and Minor Number = 0, however once the configuration of the associated Mark 6 control system
EGD exchange is completed the user will need to re-visit the Configuration Signature of the particular /91
Produced EGD exchange and manually enter the control system Configuration Signature values and then re-
download the new configuration to the 3500/91 EGD module.
Each time a change is made to the Mark 6 control system EGD exchange that is associated with a particular
/91 Produced EGD exchange device the Configuration Signature in the Mark 6 control system will change.
When this happens the user will need to go back to the particular /91 Produced EGD exchange and manually
update the Configuration Signature and then re-download the new configuration to the 3500/91 EGD
module.
Once the above configuration is completed do not select OK. Keep this configuration screen open to
configure the 3500/91 module EGD Produced Exchange. If after you complete the above configuration and
select OK you will need to right click on the 3500/91 module again and select Options.
Note:
In later steps you will need to download the new configuration to the 3500/91 EGD module.
If the single 3500 Rack contains two 3500/91 EGD modules then it is best to download them one at a time.
14.6 Assigning Points to the 3500/91 EGD Produced Exchange(s)
The /91 EGD module provides four (4) produced EGD exchanges. They are labeled Produce 1, Produce 2,
Produce 3, and Produce 4. These exchanges can consist of Floating Point and Boolean data that contain
configurable sets of measurement values and statuses from the other monitors in the 3500 rack
The following points are available for the four (4) /91 Produced EGD exchanges:
• Module and Channel Status (two bytes)
• Module Switch and Channel Switch (two bytes)
• Proportional Values (PPLs) and Setpoint such as Alert & Danger (four bytes)
The Status and Switch are composed of Boolean bit fields’ two byte data (Integers) that indicate a state for a
given property.
Proportional Values and Setpoints are also known as Floating Point four byte data (Real Numbers)
Proportional Values – Data values such as Direct, Gap, 1X amplitude, etc…
Setpoints – Levels of a proportional value at which a channel will toggle an alarm status such as
Alarm 1 (Alert), and Alarm 2 (Danger) - Over and Under.
Each of the four (4) /91 Produced EGD exchanges are limited to a total of only 1,380 bytes of data per each
exchange.
Proportional Values and Setpoints known as Floating Points four byte data or Real Numbers are limited to
1380/4 = 345. This means that a single /91 Produced EGD exchange is limited to 350 Proportional Values
and Setpoints.
Module / Channel Status and Switches known as Boolean bit field two byte data or Integers are limited to
1400/2 = 700. This means that a single /91 Produced EGD exchange is limited to only 700 Module / Channel
Status and Switches.
The /91 Produced EGD exchanges, Produce 1, Produce 2, Produce 3, and Produce 4 can have a combination
of four byte Real Numbers - Proportional Values and Setpoints as well as two byte Boolean bit field Integers -
Status and Switch.
In most cases the data from the 3500 to the Mark VIe control system will be four byte Real Numbers -
Proportional Values and Setpoints.
The user should populate the first /91 Produced EGD exchange Produce 1 with the data that is to be sent to
the Mark VIe controller and then create the associated Mark 6 EGD exchange EXCH1.
If the data exceeds the 13,80 byte limitation for the single /91 Produced EGD exchange then you would utilize
the remaining /91 EGD exchanges, Produce 2, Produce 3, and Produce 4 and then create the associated
Mark VIe EGD exchanges – EXCH2, EXCH3, and EXCH4.
The correlation between the /91 Produced EGD exchanges and the Mark VIe EGD exchanges is as follows:
/91 Produced EGD exchange Produce 1 = Mark VIe EGD exchange EXCH1
Use the following as a general guide when configuring the /91 Produced EGD exchange(s).
A Single 3500 Rack with a Single 3500/91 EGD Module

Number Of /91 Produced EGD Exchange(s) Point Total (Per EGD Exchange) Time Interval (ms) (Per EGD Exchange)
1 = Produce 1 0 – 175 Points 60 (ms)

2 = Produce 1 & Produce 2 0 – 175 Points 100 (ms)
3 = Produce 1, Produce 2, & Produce 3 0 – 175 Points 120 (ms)
4 = Produce 1, Produce 2, Produce 3, & Produce 4 0 – 175 Points 160 (ms)

A Single 3500 Rack with Dual – Redundant 3500/91 EGD Module(s)

Number Of /91 Produced EGD Exchange(s) Point Total (Per EGD Exchange) Time Interval (ms) (Per EGD Exchange)


3 = Produce 1, Produce 2, & Produce 3 N/A N/A
4 = Produce 1, Produce 2, Produce 3, & Produce 4 N/A N/A
Note:
• Four Byte Real Numbers are used for Point Totals, however the point configuration can be a mixture
of floating Point four byte data (Real Numbers) and Boolean bit fields’ two byte data (Integers).
• In later steps you will need to download the new configuration to the 3500/91 EGD module.
• If the single 3500 Rack contains two 3500/91 EGD modules then it is best to download them one at a
time.
If the Time Interval (ms) is set to low for the number of Points you are trying to configure per the /91
Produced EGD exchange(s) you will get an error as shown below:
Use the following strategies to remove this error:
• Reduce the number of configured points. This will reduce the run time for a given exchange and in
turn reduce the aggregate run time.
• Increase the time interval for each active exchange. This will increase the maximum allowed time,
and let more points be configured.
• Deactivate unnecessary exchanges. This will reduce the number of exchanges used to calculate the
aggregate run time, and help reduce the aggregate run time to less than the total run time.
Once the basic configuration information has been completed for the 3500/91 EGD Comm Gateway module
you will need to add the data/tags (Points) to the 3500/91 EGD Produced Exchange pages.
1. Select Points from the 3500/91 configuration.
The blank Exchange Points page requires configuration.

2. The buffers of each produced exchange can contain the following types of 3500 data from the rack:
setpoints, proportional values, device/module status, channel status, module switches, and channel
switches. This section shows how to use the point configuration dialog to assign data to the produced
exchanges.
The buffers of each produced exchange can contain the following types of 3500 data from the rack:
setpoints, proportional values, device/module status, channel status, module switches, and channel
switches. This section shows how to use the point configuration dialog to assign data to the produced
exchanges.
To assign 3500 data to an exchange register:

1. Click on the monitor in the virtual rack (1) that contains the data to be assigned. The available points for
the selected monitor will appear in the Points Selection Tree (3).
(4) Notice that the nodes in the tree can be expanded or collapsed to reveal the hierarchy of data for the
selected monitor.
2. Assign data in the selected monitor by dragging points from the Points Selection Tree (3) to the Points
Configuration List (2). Notice that you can assign multiple points to contiguous registers by dragging an
upper-level node from the selection tree to the list. All points in the hierarchy below the
node will be copied to the list.
Note: The Point Names are fixed – pre-set – by the 3500 system and cannot be changed.
Once all of the points are configured select OK
14.7 Exporting the 3500 Report File

Once selecting OK from the above step the 3500/91 EGD Comm Gateway configuration screen will appear.
Once the data/tags (Points) for the 3500/91 EGD Produced Exchange(s) have been configured the user
should export each /91 Produced EGD Exchange Report so the it could be utilized the Mark VIe – 3500 Rack
EGD Produced Page.
1. Left mouse click on Report, name the file, and save as a .txt file to the Desktop.
14.8 3500/91 Module EGD Report Configuration
The next steps involve manipulating the saved 3500/91 Module EGD Report information so that it can be
utilized in the Mark VIe - ToolboxST – EGD Produced Page format.
When the Mark VIe - 3500/91 EGD Produced Exchange – BN3500R1_PG1 was configured the Columns were
organized as: Name – Location – Description – Units – Type – Exchange ID. These columns will need to be
added to the saved 3500 – EGD - Report
1. Open the saved 3500-EGD-Report as a Data Excel worksheet. Delete the CIRCLED highlighted
columns and their contents. The Column items UNITS – Point Description – ADDRESS and their contents
should remain.
2. The Columns for the Produced EGD page - BN3500R1_PG1 – Name – Location – Description – Units
– Type – Exchange ID should be added to the saved 3500 – EGD – Report as well as moving the data under
the remaining columns that were not deleted under the new added columns.
A Name must be given to each individual signal. The Name must be unique for each signal and contain no
spaces.
The item ADDRESS that was not removed in step 8 should be placed under the new column of Location
The item Point Description that was not removed in step 8 should be placed under the new column of
Description
The item UNITS that was not removed in step 8 should be placed under the new column of Units
Each signal Type will need to be defined such as BOOL, DINT, INT, LREAL, REAL, UDINT, UINT. Most signals
should fall under the Type category of REAL.
The Exchange ID should be set to the 3500 EGD Header – In this example looking at the top left information
item #6 Exchange Number: 1 = Exchange ID = 1
The 3500 91 module has the ability to provide four (4) Produced EGD pages. If the other produced pages are
used then the Identifier should be set to:
Produced 2 – Exchange ID = 2
3. Once the saved 3500-EGD-Report has been properly configured the information – tags / signals –
listed under each column would then need to be transferred to the new 3500 external device EGD
Produced Page.
If the configuration of the 3500/91 module Report file was done on another computer than that Excel file will
need to be transferred to the HMI operator interface computer.
The information you are about to copy will need to be pasted into the new 3500 external device EGD
Produced Page therefore that page will need to be revisited. (see the section 3500/91 Produced EGD Page –
Step 9 – Page 11)
Copy the manipulated information tags/signals (outlined in red) from the Report Excel file:
4. Go to the new 3500 external device EGD Produced Page and left mouse click on the section below
the Location column and then select the Paste tab. This should past the copied and or manually
entered tag information from the 3500 Excel data workbook.
5. The 3500 tags should now be placed in the 3500 Produced page similar to what is shown:
6. Perform a Build operation for the new 3500 tags.

Once the 3500/91 EGD External Points data/tags have been entered into the new 3500 external
device EGD Produced Page created in Workstation ST a Bind operation and save must be performed.
The Bind action should result in no errors. Correct any errors if shown.
This should complete the process of adding a new 3500 device and it’s associated the EGD
Produce Page to the Mark VIe Workstation ST configuration.
The 3500 Rack should now be a part of the control system and data/tags from the 3500 are now
available on the EGD via the Unit Data Highway Ethernet network.
IMPORTANT NOTE:
Once the above step is completed this new external device EGD Produced Page will produce a
new Major and Minor Signature values.
These new Major & Minor Signatures will need to be updated on the 3500/91 EGD Module. This is
a manual step that will require one to:
1. Open the .rak file and Select the /91 Communication Gateway Module
2. Select Options
3. Manually enter the Major and Minor Signature values.
4. Select OK.
5. Download the new /91 configuration to the 3500 Rack.
These steps are covered in sections: Configuring the 3500/EGD Module and Downloading the new
3500/91 EGD Module Configuration.
15. Control System HMI Configuration

The following should be configured in the control system HMI computer that contains the Master file.
15.1 Host File

Add the 3500/91 EGD module to the HMI operator interface computer HOST file.
Right click on My Computer and select the C:\ drive Navigate to: WINDOWS | system32 | drivers \ etc
The control system Boiler Plate Host file version 7.0 lists IP Addresses 192.168.101.74 – 192.168.101.88 as
“Reserved for Bently - Future use “. Based on this information, in this example we will use the .74 IP address
for our single 3500 Rack with a 3500/91 EGD module, however it would be best to check the HOST file in the
control system HMI operator interface computer on your particular system to determine the available UDH IP
address to meet your systems specific requirements.
Example: One gas turbine unit and a single 3500 Rack with a 3500/91 EGD module.
192.168.101.74 BNR1 #Bently Nevada 3500/91 Rack 1 For Unit GT1
Multiple 3500 Racks should be separated by the naming convention: R1, R2, R3 etc…
15.2 CONFIG.DAT
Modify the Config.dat file to include the 3500 Rack with a 3500/91 EGD module. Right click on My Computer
and select the E:\ drive Navigate to: Site
In the example below we have one (1) gas turbine unit with an Exciter and a single 3500 Rack having a single
3500/91 EGD modules. NOTE: The Unit Type for the 3500 should be set to MARKVI
• Enter the 3500/91 under the next unused Unit Number….
• Make sure to remove the semicolon to the left of the Unit_Data – Unit Number
16. Using the 3500/91 EGD Data/Tags in the Control System Code
With steps 10 thru 13 completed the 3500/91 EGD module data/tags would be available for use in the Mark
VIe control code, depending on the customers/applications specific need (less use as primary means of
turbine unit trip functionality).
It is also at this point where the Mark VIe trend application could be used to trend any of the 3500/91 EGD
module data/tags.
If the Mark VIe is to be configured to trend the 3500/91 EGD module data/tags then an update to the
Mark VIe will most likely be required.
It is IMPORTANT the user understand what is necessary when an update to the Mark VIe is required. Please
see Section 5 Mark VIe Control Upgrade for more information.
If the 3500/91 EGD module data/tags are to be used in the Mark VIe control system application code then it
is recommended that the Health of the 3500 Rack system should be incorporated to avoid the Mark VIe
control system taking action on invalid and or stale data.
The 3500 Rack first must be configured in the Mark VIe controller as a Referenced Device.
From the WorkstationST system editor screen select the Mark VIe controller and double click on the on the
Mark VIe controller.
A dialog box should appear as shown below:
Select the EGD tab
Right click on Referenced Device and select Select Devices

Select the 3500 Rack device ( BN3500R1) and then select OK
In the EGD section now will show the 3500 as a Referenced Device.
In this example we have configured the 3500 system to provide four (4) Health status signals/tags.
However, adding the 3500 as a Reference Device creates an inequality between the WorkstationST
application code on the HMI computer and the application code stored in the Mark VIe controller.
With the Controller Equality Not Equal the user must perform a Build operation.
If no errors after the Build operation the last line should be similar to the one shown below.
The next step would be to perform a Download operation to the controller.

After selecting Download the following dialog box will appear. Select Next
The next dialog box will show that the Application Code will be downloaded, select Next
It is recommended that the Download Backup File is checked. Then Select Next
Depending on the type of change and the connection to the Mark VIe controller you will get different
download messages.
Online Download Message
Offline Download Message

Select Yes
Select Finish when download is completed.

16.1 3500/91 EGD Data/Tags Health Verification

If the 3500/91 EGD module data/tags are to be used in the Mark VIe control system application code then it
is recommended that the Health of the 3500 Rack system should be incorporated to avoid the Mark VIe
control system taking action on invalid and or stale data.
The following section provides a general overview of what 3500 data/tags could be use, how to
incorporate these 3500 data/tags into the 3500/91 EGD module and Mark VIe control system.
The example will be examining the 3500/22 TDI module and only one (1) 3500/42 Module, however if
the data/tags being used in the control code are from other /42 modules within the 3500 Rack then the
signals being used for the single 3500/42 module in this example can be used and are available from
any additional 3500/42 modules.
The 3500 data/tags being used are provided in the Module Status and are:
3500/22 TDI\RIM Not OK This signal provides status if the /22 TDI module fails.
3500/42 Not Ok This signal provides status of the /42 module Probe.
3500/42 Channel Not Ok This signal provides status of the /42 module Channel.
3500/42 Channel Not Monitoring This signal provides status if the /42 module fails.
Load the .rak file for the 3500 system. From the System Configuration Utility Select File – Open – The default
location for the .rak file is – C:\3500\Trains\Primcfg Once the .rak file is loaded connect to the 3500 Rack:
Once connected to the 3500 Rack right mouse click on the 3500/91 module and select Options
Assuming that the basic configuration information has been completed for the 3500/91 EGD Comm Gateway
module you will need to add the data/tags (Points) to the 3500/91 EGD Produced Exchange pages.
Select Points from the 3500/91 configuration.
Drag the Module Status for the Slot 1 device, which is the 3500/22 TDI module to the Exchange Points.
The signal that provides status if the /22 TDI module fails is within this Module Status information.
Select the /42 module in slot 2 and drag the Module Status for the device to the Exchange Points.
The signal that provides status of the /42 module Probe is within this Module Status information.
For the same /42 module expand Channel 1 – C01. Once Channel 1 is expanded select the Status and drag it
to the Exchange Points.
The signal that provides status of the /42 module Channel as well as providing status if the /42 module
fails is within this Module Status information.
Once all of the points are configured select OK. Following the steps outlined in section 10.7 Exporting the
3500 Report File we can examine the data/tags needed.
Follow the steps outlined in Section 11 – 11.3 for adding these four signals to the produced EGD exchange of
the 3500 – Workstation.
Section 14 then covers how you would add the 3500 Workstation, and its associated produced EGD
exchanges, to the Mark VIe control system.
This example both of the above have been completed so that we have four (4) signals defined in the 3500
Workstation produced EGD exchange and the 3500 is not a Reference Device in the Mark VIe, which will alloo
the user to utilize the signals/tags defined in the 3500 produced EGD exchange in the Mark VIe application
code.
TDI/RIM Not Ok = BN3500R1.TDI_OK This signal provides status if the /22 TDI module fails
Not Ok = BN3500R1.Probe1_S2C1 Signal provides Probe status for /42 module Slot2 Channel 1
Channel Not Ok = BN3500R1.Chan_Mod2_ok This signal provides status of the /42 module Channel.
Channel Not Monitoring = BN3500R1Module_2_OK This signal provides status if the /42 module fails.
Assuming that the 3500 Workstation has been configured correctly, the signals should be available to be
used in the mark VIe control application code.
If the Mark VIe control application code is utilizing data/tags from the 3500 system via the 3500/91 EGD
module then it is recommended that the health of the 3500 system be incorporated into the Mark VIe
application code utilizing the data/tags from the 3500 system. The Mark VIe control system should not take
action on stale or unhealthy data inputs from the 3500 system.
If the Mark VIe application code is utilizing a particular signal from the 3500 system that is associated with a
particular 3500 probe then the health status of the 3500 probe signal, which includes the module input
channel associated with the probe, the input module itself, and the /22 TDI health status should be
incorporated in the Mark VIe application code. Doing so will provide a level of health validity to the in data
from the 3500 system.
The following provide a sample of how these health data/tags could be brought into the Mark VIe,
however the sample DOES NOT specify how these signals are to be used in the Mark VIe application
code.
Under the Software tab the user would Add Task, Add Block, and then Add signals to the Variables
In the following example we have created a Health Status Task (BN3500R1_Health_Status_) and
MOVE_1 blocks, and signals in our Variables under our Task.
The signals we added in the Variables were Mark VIe control system specific “mirrored” signal that
were created for each of the 3500 data/tags.
The following provides more detail for each of the MOVE_1 blocks.
BN3500R1.TDI_OK Signal from the 3500 Rack via the 3500/91 EGD module
3500_TDI_OK M ark VIe “ mirrored” signal of the 3500 signal.
------------------------------------------------------------------------------------------------------------
BN3500R1.Probe1_S2C1 Signal from the 3500 Rack via the 3500/91 EGD module
3500_Probe1_S2C1 M ark VIe “ mirrored” signal of the 3500 signal.
-----------------------------------------------------------------------------------------------------------
BN3500R1.Chan_Mod2_OK Signal from the 3500 Rack via the 3500/91 EGD module
3500_Chan_Mod2_OK M ark VIe “ mirrored” signal of the 3500 signal.
BN3500R1.Module_2_OK Signal from the 3500 Rack via the 3500/91 EGD module
3500_Module_2_OK M ark VIe “ mirrored” signal of the 3500 signal.
16.2 VAR_HEALTH Block –

In addition to using the above data/tags for health verification of specific signals from the 3500 system the
Mark VIe VAR_Health block code should also be used to verify the health any and all data/tags being
consumed by the Mark VIe control system from the 3500 system and used in the Mark VIe application
code.
16.3 Consumed EGD Exchange Health Status
The Mark VIe controller uses a single signal to verify the health of all consumed EGD exchanges. This signal
Called, IsUdhEgdHealthy, coupling this signal with the VAR_HEALTH block will provide health status
information of the consumed 3500/91 EGD exchange.
16.4 HMI Configuration – Referenced Devices – CIMPLICITY Project

Points
To display the 3500 data/tags on a control system HMI operator interface computer requires the new 3500
device to be added as a Referenced Device to the HMI operator interface computer (Workstation) that is the
OPC DA Server for the system. This will also requires that the HMI Device – HMI – HMI Config is selected in
the HMI operator interface computer as well.
It is assumed that the following steps have already been configured during the initial project engineer of the
HMI computer. Steps 1-3 below are more or less for verification.
1. In the main Tree View double click on the HMI (workstation) computer. In this example the HMI is
labeled as the Control Room HMI Server CRM1_SVR .
2. Under the General Tab -- Features -- under the Enabled column verify HMI is set True.
3. Under the HMI Config Tab – HMI – verify Project File Path is set to the Cimplicity .gef file location
relative to the project you are working on.
4. Under the General Tab select Consumed Devices under the Referenced column the new 3500
external device is set True.
5. To complete the process – first perform a Build – then assuming no Build errors a Download – and
then assuming no errors Save the new HMI configuration to the system.
Download Step Note: The initial creation of the new 3500 External Device, Produced EGD data/tags from the
3500/91 module, and addition to the HMI Workstation as Consumed Device will cause a difference in the
running application code.
Select Next >
Select Next >

Select Yes >
When the download is completed select Finish

16.5 CIMPLICITY Project Points
With the HMI computer HMI Config configured properly and the Consumed Devices now configured to
the new 3500 External Device the Produced EGD data/tags from the 3500/91 module should be
available to the CIMPLICITY project.
A. If the CIMPLICITY project was running during the time of the adding of the new 3500 external
device and all of the above associated configuration one would have to select Refresh under
the Workbench View Tab.
B. The new 3500 External Device should be present in the project Points listing:
C. The new 3500 External Device contains the 3500/91 module Produced EGD data/tags that were
configured in Step 3 of Assigning Points to the 3500/91 EGD Produced Exchange.
D. If the CIMPLICITY project was NOT running during the time of the adding of the new 3500
external device and all of the above associated configuration select Run and then one would
have to select Refresh under the Workbench View Tab.
Opening CIMPLICITY Workbench and selecting the .gef file relevant to the project configuration – in
this example the .gef file is CRM1SVR.gef
Select Run
Select Yes
The new 3500 External Device as well as the associated Produced EGD data/tags should be present in
the project Points listing:
16.6 Adding Tags to the 3500 External Device Produced EGD Page
If after adding the new 3500 external device and associated Produced EGD data/tags you wish to add an
additional data/tag point(s) to the 3500/91 module in order to display on an HMI screen.
1. Add the new tag(s) following the steps outlined in Section Assigning Points to the 3500/91 EGD
Produced Exchange. (Page 16 Steps 1-3)
2. Continue the process by following the steps outlined in Section: Downloading the new 3500/91 EGD
Module Configuration. ( Page 19 – Steps 1-6)
If only one new tag is added to the 3500/91 EGD Produced Exchange than one should manually enter that
tag information to the Mark VIe External Device – follow similar to Step 4 – 6 of Section 3500/91 Module EGD
Report Configuration.
If multiple additional tags are added then one may want to follow all of the steps 1 – 6 listed in the 3500/91
Module EGD Report Configuration section.
Note:
Once you have added the new tag(s) and performed a Bind Consumed, build and Produced published
to the configuration server to the External Device Produced EGD Page the Major & Minor Signature for
that page will updated.
With the Major & Minor Signals updated you will have to go through the process of updating the
3500/91 EGD Module Major & Minor Signatures.
These steps are covered in sections: Configuring the 3500/EGD Module (Pg 12 - Steps 1-3) and
Downloading the new 3500/91 EGD Module Configuration (Pg 19 – Steps 1-6)
16.7 Updating the HMI Referenced Device
Now that the new tag(s) have been added and configured in the 3500/91 EGD Module as well as added and
configured to the External Device EGD Produced Page you will need to update the Referenced Device of the
HMI operator interface computer (Workstation) that is the OPC DA Server for the system.
1. In the main Tree View double click on the HMI (workstation) computer. In this example the HMI is
labeled as the Control Room HMI Server CRM1_SVR .
2. Under the EGD Tab – Under the Referenced Devices - right click on the 3500 External Device
and select Refresh.
Selecting Refresh will import the new Produced EGD Page, which included the new tag(s) you have
added, from the 3500 External Device.
You can perform a Build Configuration and Download, however when you just Refresh a Referenced
Device the application code does not change.
Therefore when performing the Download step you will get green =
Select Cancel
With the application code equal you will have to manually push the new tag(s) into the CIMPLICITY
project so that they can be new Points.
3. Select the Workstation ST monitor, which should be located in the lower right corner, near the
PC clock.
4. Select HMI – right click on HMI and select Start Sub-Features

Select Importer and then OK

You should see the Additional Information change from Hmi Importer is Ready to Import
Hmi Importer is Running
Note: This action may take a few minuets to switch and run.
Once completed it will switch back to read Hmi Importer is Ready to Import
If there are any errors or if you wish to see the completed task – right click on
Hmi Importer is Ready to Import
With no errors the new tag(s) should now be available as Points in the CIMPLICITY .gef Project.
Section CIMPLICITY Project Points (Pg28 A thru D) provides instructions on how to access/view the new
tag(s) in the CIMPLICITY .gef Project.
17. Troubleshooting
The most common errors are differences between the Mark VIe 3500 Workstation file and 3500/9
EGD Configuration.
1. EGD Exchange Size
2. Configuration Signature
3. Exchange ID
These errors are usually present when signals in the Live Values column are RED with a Red U next to each
signal as shown in the screen shot of a Mark VIe file for the 3500 produced EDG exchange, below.
--------------------------------------------------------------------------------------------------------
1. EGD Exchange Size
• The EGD Exchange size must match between the Mark VIe control system
3500/91 Produced EGD exchange.
• If you add or remove points(s)/signals(s) from the Mark VIe control system
3500 Workstation file then you must add or remove the same number of points(s)/signals(s) from the
3500/91 EGD Produced Page.
• If you add or remove points(s)/signals(s) from the 3500/91 Produced EGD Page then you must add or
remove the same number of points(s)/signals(s) from the Mark VIe control system 3500 Workstation
file.
Example:
In the below example the 3500 Workstation produced EGD exchange contains 10 signals on BN3500R1_PG1.
These signals are REAL numbers with each signal consisting of 4 bytes.
With 10 signals at 4 bytes per signal the total Exchange Size (Length) in bytes for BN3500R1_PG1 would be
equal to 40.
The screen show below is from the 3500.91 EGD module REPORT viewed in Excel.
The (byte) column was added to show that each of the 10 REAL number signals are 4 bytes in length which
provide for a total of 40 bytes for the 3500/91 EGD Produce 1 exchange.
2. Configuration Signature
The Configuration Signature - Major & Minor - must match between the
Mark VIe control system 3500 Workstation file and the 3500/91 Produced EGD exchange.
Example:
The Mark VI control system 3500 Workstation file Configuration Signature is set to 102.0.
The Major Signature = 102
The Minor Signature = 0
-----------------------------------------------------------------------------------------------------------
The 3500/91 EGD module Configuration Signature is set to 0.0
The Major Signature = 102

The Minor Signature = 0
3. EGD Exchange ID
The EGD Exchange ID must match between the Mark VIe control system
3500 Workstation file and the 3500/91 Produced EGD exchange.
Example:
The Mark VIe control system 3500 Workstation file Exchange ID = 1
-------------------------------------------------------------------------------------------------
The 3500/91 Produced EGD exchange is set to = 1

EGD Mark VIe Integration Procedure

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EGD Mark VIe Integration Procedure

Uploaded by

Copyright:

Available Formats

BENTLY NEVADA No.

179842 Rev A Page 1 of 69

7. Software Backups ..................................................................................................................... 6

8. Item(s) Not Covered .................................................................................................................. 7

9. Mark VIe – TMR or Dual Configuration - Consumed EGD Limitation..................................... 8

10. Mark VIe – SIMPLEX Configuration - Consumed EGD Limitation.......................................... 8

11. 3500 Group Action Commands ................................................................................................ 9

12. Adding a 3500 Rack as a External Device ............................................................................... 9

13. 3500/91 Produced EGD Page.................................................................................................. 14

14. 3500 Rack Configuration ........................................................................................................ 18

15. Control System HMI Configuration ........................................................................................ 34

GE Control System Documentation

Rack Configuration Software

6.1 Mark VIe Control System

6.2 Bently Nevada 3500 Monitoring and Diagnostic System

7.1 Mark VIe Control System HMI

File Type File Location

7.2 Bently Nevada 3500 Monitoring and Diagnostic System

3500 System Configuration (.rak)

8. Item(s) Not Covered

9. Mark VIe – TMR or Dual Configuration - Consumed EGD Limitation

10. Mark VIe – SIMPLEX Configuration - Consumed EGD Limitation

11. 3500 Group Action Commands

12. Adding a 3500 Rack as a External Device

13. 3500/91 Produced EGD Page

Enter Page Name in dialog box and then select OK

When done click OK

13.1 New 3500 External Device Produced EGD Page Configuration

13.2 Manual 3500/91 Module Produced EGD Page Configuration

13.3 .CSV File 3500/91 Module Produced EGD Page Configuration

14. 3500 Rack Configuration

14.1 Configuring the 3500/91 EGD Module:

There are two standard ways of connecting to a 3500 rack:

• Ethernet connection to the 3500/22 TDI module.

14.2 Direct Connection - RS232

14.3 Using the Rack Configuration Software

Start | Programs | 3500 Software | Rack Configuration Software

14.4 3500/91 EGD Module Basic Device Configuration

Source IP: 192.168.101.74

14.5 3500/91 Produced EGD Exchange Configuration

14.6 Assigning Points to the 3500/91 EGD Produced Exchange(s)

Proportional Values – Data values such as Direct, Gap, 1X amplitude, etc…

A Single 3500 Rack with a Single 3500/91 EGD Module

1 = Produce 1 0 – 175 Points 60 (ms)

1 = Produce 1 0 – 350 Points 60 (ms)

A Single 3500 Rack with Dual – Redundant 3500/91 EGD Module(s)

1 = Produce 1 0 – 175 Points 60 (ms)

1 = Produce 1 0 – 350 Points 60 (ms)

Use the following strategies to remove this error:

1. Select Points from the 3500/91 configuration.

The blank Exchange Points page requires configuration.

To assign 3500 data to an exchange register:

14.7 Exporting the 3500 Report File

14.8 3500/91 Module EGD Report Configuration

6. Perform a Build operation for the new 3500 tags.

15. Control System HMI Configuration

15.1 Host File

• Enter the 3500/91 under the next unused Unit Number….

A dialog box should appear as shown below:

Select the EGD tab

Right click on Referenced Device and select Select Devices

Select the 3500 Rack device ( BN3500R1) and then select OK