Ge9 Opc Server

GE9 OPC Server
October 2008
All rights reserved. No part of this publication may be reproduced in any form or by any electronic or mechanical
means, including photocopying and recording, without permission in writing from GE Fanuc Intelligent Platforms, Inc.
Disclaimer of Warranties and Liability

The information contained in this manual is believed to be accurate and reliable. However, GE Fanuc Intelligent
Platforms, Inc. assumes no responsibilities for any errors, omissions or inaccuracies whatsoever. Without limiting the
foregoing, GE Fanuc Intelligent Platforms, Inc. disclaims any and all warranties, expressed or implied, including the
warranty of merchantability and fitness for a particular purpose, with respect to the information contained in this
manual and the equipment or software described herein. The entire risk as to the quality and performance of such
information, equipment and software, is upon the buyer or user. GE Fanuc Intelligent Platforms, Inc. shall not be liable
for any damages, including special or consequential damages, arising out of the user of such information, equipment
and software, even if GE Fanuc Intelligent Platforms, Inc. has been advised in advance of the possibility of such
damages. The user of the information contained in the manual and the software described herein is subject to the GE
Fanuc Intelligent Platforms, Inc. standard license agreement, which must be executed by the buyer or user before the
use of such information, equipment or software.
Proprietary Notice
The manual and software contain confidential information which represents trade secrets of GE Fanuc Automation
and/or its suppliers, and may not be copied or disclosed except as provided in the license with GE Fanuc Automation.
The information in this manual is subject to change without notice and should not be construed as a commitment by GE
Fanuc Automation. GE Fanuc Automation assumes no responsibility for any errors that may be in this document.
Notice
©2008 GE Fanuc Intelligent Platforms, Inc. All rights reserved. *Trademark of GE Fanuc Intelligent Platforms, Inc.
Microsoft® is a registered trademark of Microsoft Corporation, in the United States and/or other countries.
All other brands or names are property of their respective holders.
Version 7.19 – 06.05
We want to hear from you. If you have comments, questions, or suggestions about our documentation, send them to the
following email address:
doc@gefanuc.com
Table of Contents
About the GE9 I/O Driver..................................................................................................................1
OLE Automation Technology........................................................................................................1
Integration with the FIX .................................................................................................................1
Event-Driven Architecture .............................................................................................................2
OPC Compliance ..........................................................................................................................2
How the I/O Driver Works .................................................................................................................3
Features........................................................................................................................................5
Feature: Using the OLE for Process Control (OPC) Functionality ...........................................5
Feature: Creating Datablocks Automatically in FIX Database Builder .....................................6
Feature: Configuring the Driver from Custom COM/OLE Automation Applications .................7
Feature: Using the GE9 I/O Driver Graphical User Interface ...................................................8
Feature: Remote Control and Configuration ............................................................................8
Feature: Using Exception-Based Processing ...........................................................................9
Feature: Using Secondary Poll Rates ......................................................................................9
Feature: Phasing Poll Rates ...................................................................................................10
Feature: Enabling or Disabling Individual Channels, Devices, and Datablocks .....................10
Feature: QuickFail Logic .........................................................................................................10
Feature: Using Simulation Mode ............................................................................................11
Feature: Using Latched Data..................................................................................................11
Feature: Time/Date Stamp for Data and Alarms ....................................................................12
Feature: Running as a Windows Service ...............................................................................12
Feature: Block Writes .............................................................................................................14
Feature: Advanced Diagnostics..............................................................................................15
Feature: Multiple Messages ...................................................................................................15
Setting Up the I/O Driver ................................................................................................................17
Supported Hardware ..................................................................................................................18
Required Software ......................................................................................................................18
Operating System ...................................................................................................................18
Other Software........................................................................................................................18
Supported Protocols ...................................................................................................................19
Supported Protocol Commands .............................................................................................19
Cabling ........................................................................................................................................19
Configuring the Hardware ...........................................................................................................19
Setting up Your Computer for Ethernet Communications ..........................................................20
iii
Installing the Ethernet Card in Your Computer.......................................................................20
Installing TCP/IP Protocol Stack on Your Computer with Windows NT .................................20
Installing TCP/IP Protocol Stack on Your Computer with Windows 2000, Windows XP, or
Windows Server 2003 ............................................................................................................21
Setting up Series 90-30 PLC ......................................................................................................22
Setting Up the Series 90-70 PLC ...............................................................................................23
Testing TCP/IP Ethernet Interfaces on the Network ..................................................................24
Pinging the Interface from a Host Computer Running TCP/IP Software................................24
Determining if an IP Address Has Already Been Used ..........................................................24
Programming the Hardware .......................................................................................................24
Differences Between 6.x and 7.x Drivers ...................................................................................24
Upgrading to GE9 7.x from GE9 6.x ...........................................................................................26
Uninstalling a 6.x GE9 Driver .................................................................................................26
Installing a 7.x Driver ..............................................................................................................27
Upgrading to GE9 7.x from GE9 7.x ...........................................................................................27
Using the Power Tool .....................................................................................................................31
Features..................................................................................................................................31
Access Methods .....................................................................................................................31
Understanding the Power Tool's Graphic Interface ....................................................................32
Using the Power Tool’s Properties Viewer .............................................................................32
Using the Power Tool’s Browser ............................................................................................33
Using the Power Tool's Menu Bar ..........................................................................................34
Using Shortcut Keys ...............................................................................................................39
The Status Bar ........................................................................................................................39
Using the Power Tool’s Main Toolbar.....................................................................................40
Using the Power Tool’s Run-time Toolbar ..............................................................................40
Using the Power Tool’s Configuration Toolbar .......................................................................41
Setting Up the Power Tool's Environment ..................................................................................42
Setting the Statistics Refresh Rate .........................................................................................42
Setting Defaults for I/O Driver Configuration File Name and Path .........................................43
Making Advanced Settings .....................................................................................................43
Fields and Check Boxes .........................................................................................................44
Setting Up the GE9 I/O Driver Server Connection .........................................................................49
Fields and Check Boxes .............................................................................................................50
Network List Box .....................................................................................................................50
Remote Machine Name or TCP/IP Address Field ..................................................................50
Show This Dialog on Startup Check Box ...............................................................................50
iv
Use Local Server Button .........................................................................................................50
Use Remote Server Button.....................................................................................................50
Setting the I/O Server for Automatic Connection ...........................................................................53
Configuring Channels, Devices and Datablocks ............................................................................55
Choosing a Method for Configuring Your Driver ........................................................................55
Configuring the I/O Driver with the Power Tool ..........................................................................55
Channels.................................................................................................................................56
Devices ...................................................................................................................................57
Datablocks ..............................................................................................................................63
Setting Default Values for Channels, Devices, and Datablock Properties .............................75
Creating Datablocks Inside FIX Applications .............................................................................77
Creating Datablocks When Configuring a 7.x Driver ..............................................................78
Entering Driver Information in FIX Database Builder .............................................................78
Specifying the I/O Driver in FIX Database Builder .................................................................79
Specifying I/O Addresses in FIX Database Builder ................................................................80
Specifying Signal Conditioning in Database Builder ..............................................................82
Specifying Hardware Options in FIX Database Builder ..........................................................95
Opening the Power Tool from FIX Database Builder .............................................................96
Setting Up for Creating Datablocks Automatically in FIX Database Builder .......................... 96
Verifying New Datablocks Created in FIX Database Builder .................................................96
Saving Datablocks Created in FIX Database Builder to the Configuration File .....................98
Using I/O Driver Report Files......................................................................................................99
Example .CSV file displayed in a text editor .........................................................................100
Example of Errors Displayed in I/O Server ...........................................................................101
Running the I/O Driver ..................................................................................................................103
Viewing Statistics ......................................................................................................................103
Viewing Channel Statistics ...................................................................................................103
Viewing Device Statistics ......................................................................................................103
Viewing Datablock Statistics.................................................................................................103
Starting and Stopping the I/O Driver.........................................................................................104
Starting the I/O Driver from the Power Tool .........................................................................104
Starting the I/O Driver from the FIX SCU .............................................................................104
Setting the I/O Driver for Automatic Startup in FIX...............................................................105
Starting the I/O Driver Manually from Mission Control .........................................................106
Stopping the I/O Driver .........................................................................................................107
Checking Communication.............................................................................................................109
Optimizing the Driver ....................................................................................................................111
v
Optimizing Message Lengths ...................................................................................................111
Example ................................................................................................................................111
Eliminating Excess Datablocks.................................................................................................112
Decreasing unnecessary stress on your system ......................................................................112
Sending Multiple Messages to the PLC ...................................................................................112
Troubleshooting Your System ......................................................................................................115
How Do I? .................................................................................................................................115
How do I choose poll rates? .................................................................................................115
How do I set up for remote configuration and control?.........................................................116
How do I prevent the driver from writing to the hardware? ..................................................116
How do I create reports of my driver configuration files? .....................................................117
How do I save datablocks created in FIX Database Builder to the I/O driver configuration
file? .......................................................................................................................................117
How do I open the GE9 I/O Driver Power Tool in FIX Database Builder? ...........................117
How do I configure my driver for demand polling? ...............................................................117
How do I poll a device only when data is being accessed? .................................................118
What is the difference between access time and scan time? ..............................................118
How do I set up security for using the I/O Server remotely? ................................................119
How do I set up security when the driver runs as a service? ...............................................121
How do I force a switch between primary and back-up channels or devices using FIX? ....123
How do I enable or disable channels, devices or datablocks using FIX? ............................123
How do I write data to a datablock? .....................................................................................123
How do I run the driver in simulation mode? ........................................................................124
How do I send multiple messages to a device? ...................................................................124
Troubleshooting ........................................................................................................................124
The driver does not load .......................................................................................................125
The driver loads but does not start polling ...........................................................................126
The driver does not communicate to any devices ................................................................126
The driver is not transmitting messages ...............................................................................127
The driver transmits messages but does not receive messages .........................................127
The driver communicates to some but not all of my devices ...............................................127
The driver communicates to some but not all the datablocks for a device...........................128
I cannot connect to a remote server .....................................................................................128
I cannot see the driver in the FIX Database Builder .............................................................129
I am receiving old data in my display....................................................................................129
I am receiving overruns ........................................................................................................129
My message rate is slow ......................................................................................................130
vi
My driver stops running after a period of time ......................................................................130
I do not receive driver messages in Alarm History ...............................................................130
Automatic driver startup does not work ................................................................................130
I cannot configure the driver to send multiple messages .....................................................131
Nothing happens when I select Next Channel in Mission Control........................................132
The Most Common I/O Driver Problems ..................................................................................132
Error Codes ..............................................................................................................................132
Tools for Troubleshooting the GE9 I/O Driver ..........................................................................133
Using the Event Viewer ........................................................................................................134
Getting Technical Support ........................................................................................................135
Support for the GE9 I/O driver ..............................................................................................135
Support for the Process Hardware .......................................................................................136
Creating Custom Client Applications ............................................................................................137
Creating a Custom Application Using Microsoft Visual Basic ..................................................137
Creating a Custom Application Using C or C++ .......................................................................137
Accessing GE9 Server Data Using an OPC Client ..................................................................138
Where to Find Information ............................................................................................................139
Accessing Information ..............................................................................................................139
Using F1 Help ...........................................................................................................................139
Using the Help Index ................................................................................................................139
Using the Help Full-Text Search...............................................................................................140
Using the Help Table of Contents.............................................................................................140
Navigating in the Online Help ...................................................................................................140
Using the Help Button Bar ....................................................................................................141
Using Help Links ...................................................................................................................141
Using the Help Menus ..............................................................................................................141
Customizing the Online Help ....................................................................................................142
Annotations ...........................................................................................................................142
Bookmarks ............................................................................................................................143
Printing the Online Help ............................................................................................................143
Glossary........................................................................................................................................145
CSV File....................................................................................................................................145
Exception-based Processing ....................................................................................................145
I/O Address ...............................................................................................................................145
I/O Driver ..................................................................................................................................146
NODE:TAG.FIELD ....................................................................................................................146
Primary Database Blocks .........................................................................................................146
vii
Process Database ....................................................................................................................146
Process Database Block ..........................................................................................................146
Run-time Configuration File ......................................................................................................146
SAC ..........................................................................................................................................146
Signal Conditioning ...................................................................................................................147
SIM Driver .................................................................................................................................147
Time-Based Scan Time ............................................................................................................147
Appendices ...................................................................................................................................149
Appendix A: Channel Statistics ................................................................................................149
Channel Statistics: Active Queue Count ..............................................................................149
Channel Statistics: Number of Datablocks ...........................................................................149
Channel Statistics: Number of Devices ................................................................................149
Channel Statistics: Errors .....................................................................................................150
Channel Statistics: Overruns ................................................................................................150
Channel Statistics: Parse Queue Count ...............................................................................151
Channel Statistics: Read Count Max ....................................................................................151
Channel Statistics: Read Queue Count ................................................................................151
Channel Statistics: Receives ................................................................................................152
Channel Statistics: Retries ...................................................................................................152
Channel Statistics: Timeouts ................................................................................................152
Channel Statistics: Transmits ...............................................................................................152
Channel Statistics: Write Queue Count ................................................................................153
Appendix B: Datablock Statistics ..............................................................................................153
Datablock Statistics: Block Write Queue Count ...................................................................153
Datablock Statistics: Data Quality ........................................................................................153
Datablock Statistics: Errors ..................................................................................................154
Datablock Statistics: Last Error ............................................................................................154
Datablock Statistics: Last Error Time ...................................................................................154
Datablock Statistics: Last Read Time ...................................................................................154
Datablock Statistics: Last Write Time ...................................................................................154
Datablock Statistics: Overruns .............................................................................................154
Datablock Statistics: Receives .............................................................................................155
Datablock Statistics: Retries .................................................................................................156
Datablock Statistics: Timeouts .............................................................................................156
Datablock Statistics: Transmits ............................................................................................156
Appendix C: Device Statistics...................................................................................................156
Device Statistics: Callback Received ...................................................................................157
viii
Device Statistics: Clear To Send ..........................................................................................157
Device Statistics: Connection Count ....................................................................................157
Device Statistics: Connection Failed ....................................................................................158
Device Statistics: Connection Status ....................................................................................158
Device Statistics: Errors .......................................................................................................158
Device Statistics: Initialization Needed .................................................................................158
Device Statistics: Last Queue Sent ......................................................................................159
Device Statistics: Number of Datablocks .............................................................................159
Device Statistics: Outstanding Messages ............................................................................159
Device Statistics: Overruns ..................................................................................................159
Device Statistics: Read Queue Count ..................................................................................161
Device Statistics: Receives ..................................................................................................161
Device Statistics: Retries ......................................................................................................161
Device Statistics: TCP Status ...............................................................................................161
Device Statistics: Timeouts ..................................................................................................162
Device Statistics: Transmits .................................................................................................162
Device Statistics: Write Queue Count ..................................................................................162
Appendix D: I/O Driver Statistics ..............................................................................................162
Driver Name..........................................................................................................................163
I/O Driver Statistics: Errors ...................................................................................................163
Number of Channels .............................................................................................................163
Number of Datablocks ..........................................................................................................163
Number of Devices ...............................................................................................................163
I/O Driver Statistics: Overruns ..............................................................................................163
I/O Driver Statistics: Receives ..............................................................................................165
I/O Driver Statistics: Retries .................................................................................................165
I/O Driver Statistics: Timeouts ..............................................................................................165
I/O Driver Statistics: Transmits .............................................................................................165
Index .........................................................................................................................................167
ix
About the GE9 I/O Driver
The GE9 I/O driver is a GE Fanuc version 7.x I/O driver that provides the interface and
communications protocol between GE Fanuc Series 90-30, 90-70, PACSystems RX3i and RX7i, and
VersaMax Ethernet Programmable and Logic Controllers (PLC’s) and your process control software.
GE Fanuc version 7.x drivers incorporate the following attributes to provide flexibility and ease-of-
use:
• OLE Automation technology.

• FIX integration.
• Event-driven architecture.
• OLE for Process Control compliance.
OLE Automation Technology

Version 7.x drivers incorporate OLE Automation technology and can therefore expose their features to
scripting tools and other applications. Because the drivers are OLE Automation applications, you can:
• Create and manipulate objects exposed in the I/O Server from another application.
• Create tools that access and manipulate driver objects. These tools can include embedded macro
languages or external programming tools.
The I/O driver consists of the following OLE components:
• The I/O Server – The core executable program. The I/O Server maintains the driver's channel,
device, and datablock objects, performs all required functions for communicating with the process
hardware, and exposes the methods and properties to other applications.
• The I/O Driver Power Tool – A client application to the I/O Server with a graphical user interface.
The Power Tool accesses the I/O Server and lets you view and modify channel, device, and
datablock properties.
You can also view and modify driver properties with a custom client application developed specifically
for your system. Refer to Creating Custom Client Applications to learn more about creating your own
client application.
Integration with the FIX

GE Fanuc version 7.x drivers let you automatically add addresses to the driver configuration while you
are configuring your FIX database. When you add a block to the database that accesses a point in the
hardware that you have not configured, the point is automatically added to the I/O Server and polled
for data. Refer to Feature: Creating Datablocks Automatically in FIX Database Builder to learn how to
use this feature.
1
GE9 OPC Server
Event-Driven Architecture
Version 7.x drivers are event-based rather than time-based, reducing CPU time and increasing
performance.
OPC Compliance
Version 7.x drivers also comply with the OLE for Process Control (OPC) v1.0a standard. Any 1.0a-
compliant OPC client application can access process hardware data through the I/O Server. Refer to
Using OLE for Process Control (OPC) Functionality to learn more about the advantages of OPC.
2
How the I/O Driver Works
1. I/O Server
Is the I/O driver core. The I/O Server contains objects and interfaces that perform the following tasks:
• Maintain the I/O driver configuration.
• Read and write process hardware data.
• Expose the driver functionality through OLE Automation.
2. Server Objects
The I/O server consists of the following objects:
3
GE9 OPC Server
• Driver Object – Manages Channel Objects and the overall state of the driver.
• Channel Object – A channel is an I/O driver’s communication path. The Channel Object
contains the properties and methods that govern the behavior of a channel.
• Device Object – A device is a hardware device or station that exists on a channel. The Device
Object contains the properties and methods that govern the behavior of a device.
• Datablock Object – A datablock is an addressable portion of a device. The Datablock Object
contains the properties and methods that manage the behavior of a datablock. Datablocks in
the Server’s local memory correspond to data areas in the Common Memory DLL. When you
add new datablocks to the Server’s local memory, you also add new data areas to the
Common Memory DLL.
3. OLE Interfaces
Exposes the data and functionality of the Server to other applications.
4. I/O DLL
Provides functions for sending and receiving data to and from the process hardware.
5. Common Memory DLL
Builds the common memory, exposes its functionality to the Server and the NIO DLL, and stores and
maintains process data.
6. NIO DLL
Contains the I/O driver’s data access API. The NIO DLL has direct access to the Common Memory
DLL, providing fast and efficient read/write capability.
7. Signal Conditioning DLL
Contains the API that scales raw data to the specified engineering units.
8. I/O Driver Power Tool
Serves as a high-performance client to the I/O Server with a graphical user interface for configuring
and monitoring the driver.
9. OPC Server DLL
Accesses configuration data through the Server’s OLE Interfaces and reads or writes data through the
NIO DLL. The OPC Server DLL is a fully compliant OLE for Process Control in-process v1.0a server.
10. FIX Applications
Communicates with the I/O driver through the NIO DLL. Because the NIO DLL accesses the Common
Memory DLL directly, reading data from and writing data to FIX applications is fast and efficient.
4
GE9 OPC Server
11. OPC Client Applications
Communicates with the I/O driver through the OPC Server DLL. Because the OPC Server DLL
communicates with the NIO DLL, OPC Client applications can take advantage of the high-
performance read/write capability that the NIO DLL provides.
12. Automation Controller and COM Client Applications
Communicates with the I/O driver through the OLE Interfaces. You can design custom applications
with a COM/OLE Automation programming application such as Visual Basic, Power Builder, or
Visual C++.
13. Process Hardware
Any type of I/O device that controls a process.
Features
In addition to performance improvements, version 7.x GE Fanuc I/O drivers:
• Support OLE for Process Control (OPC).
• Let You Automatically Create Datablocks from FIX Database Builder.
• Let You Configure Custom COM/OLE Automation Applications.
• Supply a New, Easy-to-Use Graphical User Interface.
• Provide Remote Configuration and Control.
• Provide Exception-Based Processing.
• Incorporate Secondary Poll Rates.
• Provide Phasing.
• Let You Enable or Disable Individual Channels, Devices, and Datablocks.
• Provide QuickFail Logic.
• Provide Simulation Mode.
• Provide Latched Data.
• Provide a Time/Date Stamp for Data and Alarms.
• Can run as a Windows Service.
• Support Block Writes.
• Provide Advanced Diagnostics.
• Provide Multiple Messages.
Feature: Using the OLE for Process Control (OPC) Functionality

OLE for Process Control (OPC) is a software standard that provides a method for business applications
to access plant floor data. The standard was developed specifically for the process control industry to
provide robust, high speed, client/server communication. The standard establishes consistency between
applications, thus simplifying system integration into a heterogeneous computing environment. The
5
GE9 OPC Server
OLE for Process Control Standard defines:

• A set of custom COM interfaces for OPC client and server writers.
• A set of OLE Automation interfaces for OPC clients developed with higher-level business
applications, such as Excel and Visual Basic. 7.x drivers do not support the Automation
interfaces.
Because OPC interfaces are designed in accordance with the OPC specification to provide a common
interface, an OPC client can connect and communicate with multiple OPC servers from one or more
different vendors, as the following figure shows.
The code that your vendor writes defines the difference between servers and specifies the following
server information:
• The devices and data that the server has access to.
• The names of data items.
• The details about how the server physically accesses the data.
The GE9 I/O driver supplies an OPC v1.0a Server DLL that serves as the OPC Interface between
OPC-aware client applications and all GE Fanuc 7.x drivers. The GE9 I/O Server has interfaces that let
the OPC Server DLL access GE9 I/O Server data. The following figure illustrates how OPC clients
work with GE Fanuc I/O Servers and the OPC Server DLL.
Feature: Creating Datablocks Automatically in FIX Database Builder

By enabling the Auto Create option in the I/O Driver Power Tool, you can automatically create
datablocks from your process control software by specifying an undefined I/O address for a database
block. Once you enter the address, the GE9 I/O driver automatically creates a datablock for it and adds
the new datablock to your driver configuration. As a result, you do not have to start the I/O Driver
Power Tool and create your datablocks before you design your process database; you need only create
the required channels and devices.
6
GE9 OPC Server
Example
1. Start the I/O Driver Power Tool and click the Setup button from the Run-time toolbar.
2. Click the Advanced tab and select Auto Create On in the Server area.
3. Close the Setup dialog box and click the Templates button from the Run-time toolbar.
4. Enter the default values you want to use for your channels, devices, and datablocks in the
Templates dialog box.
5. Using the buttons on the Configuration toolbar, add Channel0.
6. Add Device0 but do not create any datablocks.
7. Exit from the Power Tool and close all remote connections to the I/O Server.
8. Open FIX Database Builder and create five database blocks with valid I/O points using
Device0 as the device name.
9. Open the Power Tool; the Tree Browser displays the following:
Feature: Configuring the Driver from Custom COM/OLE Automation

Applications
In concert with the growing trend towards using custom programs to access plant floor data, GE Fanuc
version 7.x drivers enable you to connect easily with custom applications. You do not have to use the
GE9 I/O Driver Power Tool to configure the driver. Instead, you can create your own COM or OLE
application or use an existing OLE application (such as Microsoft's Excel) to configure the driver and
access data.
Your driver may include a custom Visual Basic application. You can use this application in place of
the Power Tool to configure your driver. You can also refer to it when creating your own custom
application. Typically, custom Visual Basic applications are created for specific needs such as:
• Customizing the way you gather and view statistics.
• Automatically building a project.
• Creating applications that control the way the driver operates.
7
GE9 OPC Server
Feature: Using the GE9 I/O Driver Graphical User Interface

The GE9 I/O Driver Power Tool is an OLE application that functions as a client to the GE9 I/O Server
and is your main graphical driver-configuration tool. It provides a graphical user interface (GUI) and
graphical aids for configuring the driver to communicate with your process hardware.
Features of the Power Tool
• Runs as a stand-alone program or can be launched from FIX.

• Lets you view channels, devices, and datablocks graphically from the Tree Browser.
• Displays run-time statistical and diagnostic information for the driver, and its channels,
devices, and datablocks.
• Provides templates for configuring default channel, device, and datablock settings.
• Provides options for customizing the Power Tool’s appearance.
• Supports remote configuration.
Refer to the following topics for a description of the Power Tool and how to use it to configure your
driver:
• About the I/O Driver Power Tool
• Setting Up the GE9 I/O Server Connection
• Adding and Modifying Channels
• Adding and Modifying Devices
• Adding and Modifying Datablocks
Feature: Remote Control and Configuration

You can control and configure the GE9 I/O Server remotely using the Power Tool or any other client
application. To set up remote control of the I/O Server, you can install the Power Tool or your client
application on a computer that does not have the server software installed. However, you must install
the I/O Server on the computer used to communicate with the process hardware.
To install the Power Tool for remote communication:
1. Insert the I/O Drivers and OPC Server CD into the remote computer’s CD-ROM drive.
2. When the start-up screen appears, click the Install Driver button.
3. Select the GE9 7.x Driver from the list and click the Install Now button.
4. Click the I Agree button to accept the user license and continue with the installation.
5. Follow the instructions on the screen to complete the installation. When the Install program
prompts you for the node type, select Client.
6. After installation is complete, open the Power Tool and connect to the I/O Server using the
Network list box. Refer to Setting Up the GE9 I/O Server Connection to learn more about
establishing a connection to the GE9 I/O Server.
8
GE9 OPC Server
Feature: Using Exception-Based Processing

GE Fanuc version 7.x drivers support exception-based processing when used with FIX products for
process control. Exception-based processing means that the software application processes data only
when the data changes beyond a datablock’s dead band.
Exception-based processing also applies to database blocks. You can enable exception-based
processing for any block in the process database. Once you enable this feature, the I/O driver reports
any data change that exceeds a datablock’s dead band to the FIX Scan, Alarm, and Control (SAC)
program. This program resides in the background and works to maintain the process database
continuously. Upon receiving notification of an exception, SAC polls for information on the affected
database block and updates that block’s value.
To configure a database block for exception-based processing:
1. Start the Power Tool and enter a value in the Deadband field of the datablock you want to
modify. For a digital block, enter a dead band of 0.
2. Start FIX Database Builder.
3. Double-click the block you want to modify from the program’s spreadsheet or select Add
from the Blocks menu and select the type of block you want to create.
4. Enter the datablock’s address in the I/O Address field of the database block.
5. Enter E in the Scan Time field of the database block.
If you have many database blocks, using exception-based processing can help reduce the demand on
SAC.
NOTE: Analog Register and Digital Register blocks in FIX databases do not support exception-based
processing. In addition, the GE9 7.x driver does not support using the Text block with exception-based
processing.
Feature: Using Secondary Poll Rates

With the GE9 I/O driver, you can specify a secondary poll rate. The driver polls a datablock at its
secondary poll rate once its access time expires. The driver remains polling at the secondary poll rate
until there is another request for data from FIX.
Using this feature, you can enter a secondary poll rate that is longer than the primary poll rate. This
9
GE9 OPC Server
configuration lets you reduce CPU time and communication requests to the process hardware while
ensuring that the datablock is always polled.
Feature: Phasing Poll Rates

Phasing staggers the times at which the I/O driver scans your datablocks. This feature prevents
overruns that may occur when the I/O driver cannot collect all the data at the specified poll rate. Use
phasing to maximize the efficiency of your driver.
How It Works
By specifying a phase, you delay the driver’s first attempt to read data from the datablock. When the
phase time expires, the driver resumes reading the datablock at the specified primary or secondary poll
rate.
Feature: Enabling or Disabling Individual Channels, Devices, and

Datablocks
You can enable or disable messaging to channels, devices, or datablocks at any time. This is a very
useful feature for debugging, maintenance, and for making preliminary configurations.
Disable a channel if
• You are removing devices on a channel for repair or maintenance and do not want to display
errors.
Disable a device if
• You are removing a device for repair or maintenance and do not want to display errors.
• You want to reduce the communications load when you do not need to collect data from that
device.
• You want to isolate the device for debugging.
Disable a datablock if
• You want to use the datablock for output only.

• You only want to intermittently view data for a datablock.
• You are experiencing a problem with a datablock.
Feature: QuickFail Logic

QuickFail Logic is inherent to GE Fanuc 's version 7.x I/O drivers. Drivers with QuickFail do exactly
that – quickly determine if there is a communication problem with a device and, if there is, bypass all
datablocks on the device. The driver intermittently attempts to read or write to the device but does not
linger on the device if it still has a communication failure. The QuickFail feature significantly
increases the efficiency of your process, especially if you have many datablocks configured on one
device.
10
GE9 OPC Server
How It Works
The driver polls a datablock on the device and experiences a communication timeout. If the driver
polls the datablock the specified number of retries and still experiences a communication timeout, it
marks the datablock as failed and sends a message to the next datablock in the queue. Any outstanding
messages for the bad device are failed immediately. Likewise, any messages in the queue intended for
the bad device and all new messages are sent only once without retries. The driver continues this
process until the communication problem with the device is resolved.
Purpose
Typically, when a message fails because of a timeout, the cause is a communication problem with the
device. QuickFail lets the driver bypass the problem device to quickly handle other device messages.
Because the driver is not spending unnecessary time on a failed device, it performs more efficiently.
Example
Reply Timeout = 05 (5 seconds)

Retries = 5
Delay Time = 5:00 (5 minutes)
Backup Device = none
The driver attempts to send a message to the process hardware. After 5 seconds, the device still has not
responded so the driver re-sends the message.
The driver tries to send the message 6 times (the first time and then the 5 retries) with 5-second
intervals between each attempt.
Each attempt fails; consequently, the driver marks the datablock as failed. If the driver has messages
for other datablocks on the same device, it sends them only once without retries.
The driver waits 5 minutes before attempting to re-establish communication with the failed device.
Feature: Using Simulation Mode

Simulation mode lets you simulate the connection of the GE9 server to the process hardware. This
allows you to develop a process database that reads and writes values to the datablock addresses that
you configure in the Power Tool without using actual process hardware. Later, when you want to
switch to real process hardware, you can do so without changing your datablocks or process database.
Simulating a connection to the process hardware is accomplished by writing values directly to the
datablocks themselves instead of sending a request to the GE9 server to write the data to the process
hardware. Likewise, values are read directly from each datablock and do not require a read request sent
to the GE9 server. These reads always return good data quality.
NOTE: Whenever you enable or disable simulation mode, close all remote connections to the I/O
Server and restart the Power Tool in order for your changes to take effect.
Feature: Using Latched Data

You can preserve a datablock’s last read by enabling the Latch Data option. Should a communication
failure occur, Data links to unlatched datablocks display a series of question marks (?????) while Data
links to latched datablocks display the last data polled. This feature is very useful when you need to
create reports about your process and require data at all times. You can also use this option to preserve
the last values on the screen after a communication failure occurs.
11
GE9 OPC Server
Example
Your control system communicates with remote devices by radio transmission. You know that radio
transmission is not always reliable (particularly during inclement weather); however, you must provide
daily reports from your process hardware.
By enabling the Latch Data option for your datablocks, you ensure data is always available for reports.
NOTES:
• FIX 6.15 does not support latched data. However, you can add support for latched data by
downloading the SAC Software Improvement Module (SIM) from GE Fanuc’s web site.
• Analog Register and Digital Register blocks do not support latched data. Consequently, we
do not recommend using these blocks with the Latch Data option.
Feature: Time/Date Stamp for Data and Alarms

GE Fanuc version 7.x I/O drivers record the time and date of the following events:
• The driver reads data from the process hardware.
• The driver writes data to the process hardware.
• An error occurs.
The driver time-stamps the data and errors at the datablock level. To view time and date stamps in the
GE9 I/O Driver Power Tool:
1. Select a datablock from the Tree Browser.
2. Click the Statistics button from the Run-time toolbar.
Feature: Running as a Windows Service

Version 7.x drivers can run as a Windows service. Running your driver as a service lets users log on
and off the operating system without shutting down the driver.
By default, an I/O Server does NOT run as a Windows service. To set up the I/O Server to run as a
service, you must register it as a service. During installation, the Setup wizard automatically registers
the server as a regular server process. To register it to run as a service, you must run the server on the
command line, specifying that you wish to register it as a service. Once the server is running as a
service, you may need to re-register it in certain situations, such as when you need to change the logon
account.
Before you register the I/O Server to run as a service, follow these steps to ensure that it is not
currently running:
• If the driver is currently running as a regular server, you must stop the process by shutting
down all clients to the server, such as the PowerTool or iFIX.
• If the driver is currently running as a service, you must stop the process by shutting down all
clients to the server, and you must also perform these tasks on your operating system:
• Windows Server 2003, Windows XP. and Windows 2000 – from Control Panel,
select Administrative Tools, then select Services. A list of all services configured on
the machine displays. Locate GE9 Server. If the status is Started, right click and Stop
the server.
• Windows NT – from Control Panel, select the Services icon. A list of all services
configured on the machine displays. Locate GE9 Server. If the status is Started, click
12
GE9 OPC Server
the Stop button.

Once you stop the server from running, select the Process tab from the Task Manager and verify that
the GE9DRV.exe process is no longer listed.
Registering the I/O Server as a Service
To register the I/O Server as a service:
1. Select Run from the Windows Start menu.

2. Enter the following command and click OK:
GE9Drv REGSERVICE
The registration process now allows the user to specify a logon account. This provides
flexibility with the user’s choice of security settings.
The Logon Account for Running As A Service dialog box appears after the user enters the
command and clicks OK:
This dialog box allows the user to select one of these accounts when registering the GE9
driver to run as a service:
• FixIOUser Account – uses the FixIOUser account to log on the I/O Server. This
conventional account uses a hard-coded password and has the necessary privileges to
log on as a service. You should not modify this account if one or more 7.x drivers
use this as the logon account when running the I/O Server as a service. If you do
modify this account, those drivers will not be able to start as a Windows service.
The FixIOUser account may not be created if it does not conform to your local IT
department’s security policies. If this account does not exist, you must select one of
the other two options.
NOTE: If you previously ran the I/O Server as a service without incident, you should
continue to run it using the FixIOUser account.
• System Account – uses the local system account to log on the I/O Server. This pre-
defined account is useful when your local IT department’s security policy requires
password expiration.
• This Account – uses an account specified by the user to log on the I/O Server. This
account is useful if you need to specify a domain account. The account used here
must be an existing account with both Administrator and Logon as a Service
13
GE9 OPC Server
privileges to run the server as a service. To determine if the account has

Administrator privileges, refer to the manual provided with your operating system.
For example, to determine Administrator privileges in Windows 2000, select
Administrative Tools from Control panel, and then select Users and Passwords. Use
the Local Security Policy Setting tool to grant the account Logon as a Service
privilege.
NOTE: In earlier versions of the GE9 driver, the I/O Server was automatically
logged on with the FixIOUser account. This logon was transparent to the user.
Once you register the driver, complete these steps:

1. Start the Power Tool and make sure the Auto Start option is enabled. Refer to Starting the I/O
Driver from the Power Tool to learn how.
2. Configure DCOM (Distributed Component Object Model). Refer to How do I set up security
for using the I/O Server remotely? to learn more.
3. If your Human-Machine Interface (HMI) software is FIX or iFIX, start FIX or iFIX. When
either program runs, it will start the GE9 server as a service.
If your HMI is a third-party package, then complete the following steps instead:
a. From Control Panel, select Administrative Tools/Services (for Windows Server
2003, Windows XP, and Windows 2000) or the Services icon (for Windows NT),
and then change the GE9 server startup from Manual to Automatic.
b. Start your HMI software.
You can reset the server to be a regular server process again by re-registering it as:
GE9Drv REGSERVER
NOTE: Before you register the I/O Server to run as a regular server, you must ensure that it is not
currently running.
When registering the server this way, it will run, perform the necessary registration work, and then
exit. You can then start the server by using more conventional methods such as starting iFIX, the
Power Tool, or any client program capable of communicating with the server.
NOTE: You cannot display the GE9 Server window using Alt + Shift + S when running as a service.
Feature: Block Writes

Block writes let you send data to various registers in the hardware at one time by using a special "send"
command. This command instructs the driver to send all outstanding writes in a single protocol
message. Block writes are useful in batch situations where multiple setup parameters are required by
the hardware at one time.
When the driver sends its outstanding writes, it also sends any unmodified values in the datablocks that
are changing using the last known value. Consequently, we recommend relatively short poll times for
datablocks you are writing to so that the driver will have the most up-to-date data.
14
GE9 OPC Server
To send block writes through FIX:
1. Create a datablock with a maximum length of 99 words (198 bytes).

2. Enable block writes in the datablock.
3. Create a Digital Output block with the following I/O address:
!Send:DataBlockName
Note that only datablock names are valid with the !Send control address. You cannot trigger block
writes using any of the following items:
• Channel and device names in place of a datablock name.
• Analog Output blocks in place of a Digital Output block.
Feature: Advanced Diagnostics

The GE9 I/O driver statistics and a data scope to help you troubleshoot any errors or problems you
may encounter. The statistics provide timeout, retries, and overruns for the driver and each channel,
device, and datablock defined. The data scope lets you see the characters being transmitted in each
message received. To display the data scope, click the Datascope button from the Run-time toolbar.
You can enable the data scope for individual channels, devices, or datablocks.
To enable the data scope for a channel, device, or datablock:
1. Right-click the channel, device, or datablock you want to modify in the Tree Browser.
2. Select Datascope On from the pop-up menu that appears.
Feature: Multiple Messages

You can improve performance of your process hardware by configuring the GE9 driver to send
multiple messages to each configured device. When you configure the driver to send multiple
messages, the PLC stores the message in a memory buffer.
Sending multiple messages to a PLC provides the best performance improvement when your process
hardware is slow or very busy because it is more efficient for the device to retrieve messages from its
memory buffer than to wait for messages to be received from the network.
You can enable this feature by changing the value in the Simultaneous Messages per Device field from
one to a value up to four. Note that unless you configure a device with at least four datablocks, the
driver cannot send four messages at once. For example, if you configure a device with two datablocks
and you set the value in the Simultaneous Messages per Device field to four, the driver will send only
up to two messages at once.
The poll time of the datablocks also affects performance. For example, if you configure four
datablocks with a poll rate of 1 second, then the driver sends four messages at once each second.
However, if you stagger the poll rates or if you phase the datablocks, then the driver will send from 0
to 4 messages depending on the poll rates.
Other factors that can affect performance include:
• The speed of the PLC CPU and Ethernet Communications Module
• The PLC scan rate
• The network load
• The number of datablocks configured for each device
15
GE9 OPC Server
• The size of datablocks (the larger the datablocks, the more time it can take to process)
Consequently, setting the Simultaneous Messages per Device field to four may not yield the best
performance. You must test various combinations of the factors listed above to determine the optimal
performance for your application. If you start receiving timeouts or the driver starts sending retries,
lower the value in the Simultaneous Messages per Device field.
To configure the driver to send multiple messages to a device:
1. Start the GE9 Power Tool.

2. Select Setup from the Option menu. The Setup dialog box appears.
3. Select the Advanced tab.
4. Double-click the Simultaneous Messages per Device field.
5. Enter the number of messages you want to send to a device simultaneously.
NOTE: Whenever you change the value in the Simultaneous Messages per Device field, stop
and restart the driver in order for your changes to take effect.
16
Setting Up the I/O Driver
The following is a general overview of the steps necessary for setting up your I/O driver.
Stage Description
1 Know your process hardware
What device does the driver communicate with?
What type of cable are you using?
What is the IP address for each device?

Note that you need to set up a unique IP address for each device. The IP
address depends on the type of network. Consult your network administrator
for the correct IP address settings.
What IP addresses do you want to connect to and what data do you want to
retrieve?
2 Choose the method of configuration
Choosing a Method for Configuring Your Driver
3 Configure the I/O driver
Adding and Modifying Channels
Adding and Modifying Devices
Adding and Modifying Datablocks
Setting Default Values for Channels, Devices, and Datablock Properties
4 Check the I/O driver status
Using Statistics Mode
5 Test driver communication with the process hardware
17
GE9 OPC Server
Stage Description
Getting Basic Communication
Supported Hardware
The GE9 I/O driver works with the following hardware:
• GE Fanuc PACSystems RX3i (does not support %W)
• GE Fanuc PACSystems RX7i (does not support %W)
• VersaMax PLC
• GE Fanuc Series 90-30 PLC and a 90-30 CMM Ethernet Interface Module.
• GE Fanuc Series 90-70 PLC and a 90-70 Ethernet Controller Module.
Required Software
Operating System
• Windows NT 4.0 with Service Pack 5 or greater.
• Windows 2000
• Windows XP
• Windows Server 2003
Other Software
• CIMPLICITY Machine Edition 5.0 or Proficy Machine Edition 5.5 and greater for
configuring the PACSystems RX3i and RX7i.
• VersaPro 2.01 for configuring the VersaMax PLC.
• TCP/IP software installed and configured on your SCADA server.
• CIMPLICITY Machine Edition 5.0, Proficy Machine Edition 5.5 and greater, or GE Fanuc
Logicmaster 90-30/20s Serial Software Package for configuring the Series 90-30 CPU and
Ethernet module.
Logicmaster 90-70 Programming Software for configuring the Series 90-70 CPU.
Series 90-70 TCP/IP Ethernet Software for configuring the Ethernet Controller for Series 90-
70 PLC’s.
NOTE: Using a Human-Machine Interface (HMI) software package is not required to use the
GE9 driver. However, if you choose to use an HMI software package, select on of the
following:
18
GE9 OPC Server
• FIX version 6.15 or greater for Windows NT.
• Dynamics version 2.1 or greater.
• CIMPLICITY HMI version 6.0 or greater*.
• A third-party HMI software package.
*NOTE: When using the CIMPLICITY OPC Client with the GE9 OPC Server, set the
AddBoolAsBool parameter to a value of 1 in the Master_OPC_X.ini file. Setting this
parameter to TRUE (1) forces the OPC Client to use VT_BOOL as the requested data type for
CIMPLICITY points of type BOOL. This .ini file is created for each OPC Client port in your
CIMPLICITY project and is located within your project's data directory.
Supported Protocols
Supported Protocol Commands
Hardware Commands Supported Used to
PACSystems RX3i Read, Write Read/Write datablock
PACSystems RX7i Read, Write Read/Write datablock
VersaMax Read, Write Read/Write datablock
Series 90-30 Read, Write Read/Write datablock
Series 90-70 Read, Write Read/Write datablock
Cabling
The GE9 I/O driver communicates to the process hardware using the Ethernet protocol. Consequently,
the driver requires a standard Ethernet cable to connect from the Ethernet card in your computer to the
Ethernet interface module in your PLC.
Configuring the Hardware

Before running the GE9 I/O driver, you need to install and configure your SCADA server and PLC for
proper Ethernet TCP/IP communications. Use the following links to learn how to configure and test
communications with your PLC.
• Setting up Your Computer for Ethernet Communications
• Setting up Series 90-30 PLC
19
GE9 OPC Server
• Setting Up the Series 90-70 PLC

• Testing TCP/IP Ethernet Interfaces on the Network
To set up communications for PACsystems or VersaMax, refer to the applicable programming
software user’s manual.
Setting up Your Computer for Ethernet Communications

The GE9 I/O driver communicates with the GE Fanuc Series 90 PLC’s through an Ethernet adapter
card installed in your computer. You can configure the GE9 I/O driver to communicate with only one
Ethernet card.
Installing the Ethernet Card in Your Computer

To properly install and configure your Ethernet adapter card, refer to the hardware’s documentation.
Under Windows 2000, Windows XP, and Windows Server 2003, you can install the Ethernet card and
the operating system should recognize and configure any necessary drivers. Under Windows NT, you
can also use the following guidelines for installing an Ethernet Interface adapter card in your
computer:
1. Switch your computer’s power off.
2. Insert the Ethernet card in your computer.
The AAUI port on the Ethernet card provides the electrical and mechanical interface to the
user-provided Ethernet transceiver cable, which connects the AAUI port to an external user-
provided transceiver. (The transceiver cable may be separate or built-in to the transceiver. The
transceiver must be IEEE 802.3 compatible.) The external transceiver is directly connected to
an Ethernet cable.
3. Switch your computer’s power on and start Windows. Log into the computer with an account
that has administrative rights. Make sure you have your Windows Installation CD or disks
nearby. The installation may require copying some uninstalled Windows files.
4. Double-click the Network icon in Control Panel.
5. Select the Adapters tab and then click Add.
6. Select the correct Ethernet adapter type for your card.
7. Refer to the documentation that came with the card to configure the correct hardware
parameters for the Ethernet card, for example, the I/O port address, Interrupt Number, and the
Transceiver type. Make sure that the values you enter match those you have configured for
the card. Also verify that the settings you select do not interfere with any other hardware
device configured in the computer.
8. Click OK to save the changes and restart Windows so that your changes take effect.
Installing TCP/IP Protocol Stack on Your Computer with Windows NT

Use the following guidelines for setting up TCP/IP under Windows NT. Refer to the Windows NT
User’s Manual for detailed instructions.
1. Start Windows NT and log into the computer with an account that has administrative rights.
Make sure you have your Windows NT Installation CD or disks nearby. The installation may
require copying some uninstalled Windows NT files.
2. Double-click the Network icon in Control Panel.
20
GE9 OPC Server
3. Select the Protocols tab and click Add.

4. Select TCP/IP Protocol from the list. Windows NT may prompt you for the location and drive
having the Windows NT Installation CD.
5. Enter the correct drive and path for the installation files.
6. Select the correct Ethernet adapter and type in the IP Address for the computer.
7. Click OK to save the changes and restart Windows NT so that your changes take effect.
Installing TCP/IP Protocol Stack on Your Computer with Windows 2000,

Windows XP, or Windows Server 2003
1. Start Windows and log into the computer with an account that has administrative rights. Make
sure you have your Windows NT Installation CD or disks nearby. The installation may
require copying some uninstalled Windows files.
2. Double-click the Network and Dial-up Connection folder in Control Panel. The Network and
Dial-up Connection window opens.
3. Right-click the Local Area Connection icon. A context menu appears.
4. Select Properties from the context menu. The Local Area Connection Properties dialog box
appears.
5. Click Install. The Select Network Component Type dialog box appears.
6. Select the Protocol from the list box and click Add. The Select Network Protocol dialog box
appears.
7. Select TCP/IP Protocol from the list. Windows may prompt you for the location and drive
having the Windows Installation CD. If this happens, enter the correct drive and path for the
installation files.
8. Select the correct Ethernet adapter and type in the IP Address for the computer.
9. Click OK to save the changes and restart Windows so that your changes take effect.
To ensure proper communication, you should obtain the values for configuring TCP/IP from your
network administrator. Also make sure that each node on the network has a unique IP address. If you
have no network administrator or you are using a simple isolated network with no gateways, you can
configure the Subnet Mask and Gateway IP addresses as 0.0.0.0. You can also use the following range
of values for assignment of local IP addresses:
3.0.0.1 First PLC
3.0.0.2 Second PLC
3.0.0.3 Third PLC
3.0.0.255 Host Computer
For proper communications, you may have to add the IP address for each device to the HOSTS file on
your system, located in the C:\WINNT\SYSTEM32\DRIVERS\ETC subdirectory.
NOTE: If the isolated network is ever connected to another network, the IP addresses 3.0.0.1 through
3.0.0.255 cannot be used. Instead, you must obtain IP addresses from your network administrator.
Likewise, the Subnet Mask and Gateway IP addresses must be set to the appropriate values for your
network.
21
GE9 OPC Server
Setting up Series 90-30 PLC

The GE Fanuc Series 90-30 Ethernet module comes with a TCP/IP stack built in. Consequently, you
only need to configure the Series 90-30 PLC with Logicmaster 90-30 Programming Software to set up
the hardware.
NOTE: The Ethernet transceiver that attaches to your PLC must be IEEE 802.3 network compatible
and must have the SQE Support test switch set to ON.
1. Install the Logicmaster 90-30 software on your SCADA server and type LM90 at the prompt.
2. Press the F2 key to access the configuration screen.
3. Create a new folder.
4. Press the F1 key to access the I/O configuration screen.
5. Complete the I/O Configuration according to the hardware configuration you have in your
PLC. Make sure to specify the various modules (numbers provided on the module) that reside
in your Series 90-30 PLC rack.
6. Configure the Ethernet Interface Module for the following fields:
• Configuration Mode – is currently fixed as TCP/IP.
• Status Address – defines the location of the LAN Interface Status (LIS) bits (16 bits)
and Channel Status bits (64 bits). The Channel Status bits are always located
immediately following the LAN Interface Status bits. Defaults to %I001
CAUTION: Do not use the 80-bits assigned to the LIS bits and Channel Status bits
for other purposes or the PLC will overwrite your data.
• Status Length – is currently fixed at 80 bits.

• IP Address, Subnet Mask, Gateway Address, Name Server IP Address – to ensure
proper communication, you should obtain the values for configuring TCP/IP from
your network administrator. Also make sure that each node on the network has a
unique IP address. If you have no network administrator or you are using a simple
isolated network with no gateways, you can configure the Subnet Mask and Gateway
IP addresses as 0.0.0.0. You can also use the following range of values for
assignment of local IP addresses:
3.0.0.1 First PLC
3.0.0.2 Second PLC
3.0.0.3 Third PLC
For proper communications, you may have to add the IP address for each device to
the HOSTS file on your system, located in the
C:\WINNT\SYSTEM32\DRIVERS\ETC subdirectory.
NOTE: If the isolated network is ever connected to another network, the IP
addresses 3.0.0.1 through 3.0.0.255 cannot be used. Instead, you must obtain IP
addresses from your network administrator. Likewise, the Subnet Mask and Gateway
IP addresses must be set to the appropriate values for your network.
Refer to the TCP/IP Ethernet Communications for Series 90-30 PLC User’s Manual (GFK-1084) for
all configuration details on setting up the Ethernet Interface Module.
22
GE9 OPC Server
Setting Up the Series 90-70 PLC

Use Logicmaster 90-70 Programming Software to configure your Series 90-70 PLC. You also need to
use the GENET System Manager to download the communications software (TCP/IP stack) to your
GE Fanuc Series 90-70 Ethernet Interface Module.
NOTE: The Ethernet transceiver that attaches to your PLC must be IEEE 802.3 network compatible
and must have the SQE Support test switch set to ON.
1. Install the Logicmaster 90-70 software on your SCADA server and type LM90 at the prompt.
2. Press the F2 key to access the configuration screen.
3. Create a new folder.
4. Press the F1 key to access the I/O configuration screen.
5. Complete the I/O Configuration according to the hardware setup you have in your PLC. Make
sure to specify the various modules (numbers provided on the module) that reside in your
Series 90-70 PLC rack.
6. Configure the Ethernet Interface Module for the following parameters:
• Configuration Mode – Select TCP/IP.
• Status Address – defines the location of the LAN Interface Status (LIS) bits (16 bits)
and Channel Status bits (64 bits). The Channel Status bits are always located
immediately following the LAN Interface Status bits. Defaults to %I001
CAUTION: Do not use the 80-bits assigned to the LIS bits and Channel Status bits
for other purposes or the PLC will overwrite your data.
• Status Length – is currently fixed at 80 bits.

• IP Address, Subnet Mask, Gateway Address, Name Server IP Address – to ensure
proper communication, you should obtain the values for configuring TCP/IP from
your network administrator. Also make sure that each node on the network has a
unique IP address. If you have no network administrator or you are using a simple
isolated network with no gateways, you can configure the Subnet Mask and Gateway
IP addresses as 0.0.0.0. You can also use the following range of values for
assignment of local IP addresses:
3.0.0.1 First PLC
3.0.0.2 Second PLC
3.0.0.3 Third PLC
For proper communications, you may have to add the IP address for each device to
the HOSTS file on your system, located in the
C:\WINNT\SYSTEM32\DRIVERS\ETC subdirectory.
NOTE: If the isolated network is ever connected to another network, the IP
addresses 3.0.0.1 through 3.0.0.255 cannot be used. Instead, you must obtain IP
addresses from your network administrator. Likewise, the Subnet Mask and Gateway
IP addresses must be set to the appropriate values for your network.
Refer to the TCP/IP Ethernet Communications for Series 90-70 PLC User’s Manual (GFK-1004) for
all configuration details on setting up the Ethernet Interface Module and refer to the Series 90 Ethernet
23
GE9 OPC Server
Communications User’s Manual (GFK-0868) for more information on the Station Manager Access
Software.
Testing TCP/IP Ethernet Interfaces on the Network

PING (Packet InterNet Grouper) is the name of a program used to test a computer’s TCP/IP interface
by sending them an echo request message and waiting for a reply. Once you have configured your
TCP/IP network, you should test each Ethernet interface available this program. When the Ethernet
interface responds to the message request, it verifies that the interface is operational and configured
properly for Ethernet TCP/IP communications.
Pinging the Interface from a Host Computer Running TCP/IP Software

You can send a ping message from any host computer running TCP/IP (since most TCP/IP
communications software provides a ping command) or from another Ethernet Interface. Under
Windows, you can send a ping message by selecting Command Prompt from the Start menu and
entering the following an the command line prompt:
PING ipaddress
If you receive a reply from the destination device, your hardware is configured properly. If you receive
a "request timed out," examine your hardware configuration and cable connections.
Determining if an IP Address Has Already Been Used

It is very important not to duplicate IP addresses. To determine if you have configured your Ethernet
Interface with the same IP address as another node on the network:
1. Disconnect the cable connected to the Ethernet Interface module).
2. Test the disconnected interface’s IP address. If you receive an answer, then the chosen IP
address is already in use by another node on the network.
3. Assign a different IP address to your Ethernet module.
Programming the Hardware

Use the following links to learn how to configure and program your process hardware:
• Required Software
• Setting up Series 90-30 PLC
• Setting Up the Series 90-70 PLC
• Testing TCP/IP Ethernet Interfaces on the Network
To set up communications for PACsystems or VersaMax, refer to the applicable programming
software user’s manual.
Differences Between 6.x and 7.x Drivers

Many of the differences between 6.x and 7.x drivers are new features. To learn more about these
features, refer to 7.x Driver Features.
24
GE9 OPC Server
The architecture of 6.x and 7.x drivers is also different. With 6.x drivers, the driver consists of two
parts: a polling portion and a configuration portion. The polling portion only does polling. The
configuration portion in turn can load, manipulate, and save configurations. With FIX or Dynamics
running, the configuration portion can load configurations without affecting which configuration the
polling portion is using. Reloading a driver configuration replaces the configuration in the polling
portion with the configuration currently loaded in the configuration portion.
With 7.x drivers, the driver also consists of two parts: a server portion and a client portion (the Power
Tool). The server portion handles polling as well as loading, manipulating, and saving configurations.
The client is simply a graphical front end that tells the server portion when to load, manipulate, save,
run, and stop. With FIX or Dynamics running, when the client (Power Tool) loads a new configuration,
it replaces the configuration in the server with the configuration just loaded. In effect, the 7.x driver
can only work with one configuration at a time. As a result, if you load a different configuration into
the Power Tool than is currently running, the current configuration being polled is replaced, and your
database tags may become invalid.
Other differences include:
• 6.x driver configuration and CSV files are not compatible with 7.x drivers and cannot be used.
• 7.x drivers no longer require the configuration to be called nodename.GE9. Instead, the
default file name is configurable.
To set the default configuration file name and change the default path:
1. Click the Setup button in the Run-time toolbar.

2. Select the Default Path tab.
3. Enter the configuration file’s default name and default path in the fields provided.
NOTES:
• A configuration file named nodename.GE9 is saved in the root Dynamics directory

when you install the driver. If you are using FIX the file resides in the Database path
(C:\FIX32\PDB, by default). Do not delete this file. FIX and iFIX use this file to load
the driver.
• If you do not enter anything in Default File Name field then FIX or Dynamics loads
a configuration called Untitled.GE9.
• If you have the Power Tool running and a driver configuration loaded with FIX 6 or later, FIX
uses the configuration you have loaded, and NOT nodename.GE9 or Default.GE9.
• The data scope in a 6.x driver is either on or off for all channels, devices, and poll records. In
a 7.x driver, you can enable and disable the data scope for individual channels, devices, and
datablocks.
25
GE9 OPC Server
To enable the data scope for a channel, device, or datablock:
1. Right-click the channel, device, or datablock you want to modify from the Tree Browser.
• Disabling a poll record has changed. In a 6.x driver, you enter DISABLED as the poll time. In
a 7.x driver, you clear the datablock’s Enable check box or enter DISABLED in the Primary
Rate field.
Upgrading to GE9 7.x from GE9 6.x

If you are upgrading from a version 6.x GE9 driver, use the following steps as a guide. Also refer to
The Differences Between 6.x and 7.x Drivers to learn what has changed.
1. Uninstall the previous version of the driver. Do not install the new version over the old
version.
2. Install the new version.
3. Add the driver to the SCADA configuration and the Task list in the System Configuration
Utility (SCU) so that the driver automatically starts when you start FIX or Dynamics.
4. If you have no process database to import, use the Auto Create option to create datablocks
automatically.
If you have a process database to import and you want Database Builder to create datablocks
for you, you can configure the driver using the Auto Create option. Do not import a CSV
version of your old driver configuration. Create a new one with the Power Tool.
If you have a process database to import and you do not want Database Builder to create
datablocks for you automatically, you can create the datablocks with the Power Tool.
Typically, you create datablocks manually when your driver configuration uses many
different data types for the same file type. For example, if you have unsigned integer data for
addresses 101 through 200 and signed integer data for addresses 1 through 100 and 201
through 300, you do not want to use the Auto Create option because it creates datablocks with
one data type, based on the selected datablock defaults.
Uninstalling a 6.x GE9 Driver

Before you install the 7.x GE9 driver, you must uninstall the 6.x driver. Do not install over the existing
6.x driver.
To uninstall a 6.x driver:
1. Open FIX Database Builder, save your existing database, and export it.
2. Export your 6.x driver configuration to a .CSV file if you want to refer to it later.
3. Open your FIX32 or Dynamics directory. The default location for FIX32 is C:\FIX32. The
default location of Dynamics is C:\Dynamics or C:\IFIX.
4. Delete or rename all the files with the name GE9*.*.
5. Delete or rename all files with the name *.GE9.
Once you delete or rename these files, you are ready to install a 7.x driver.
26
GE9 OPC Server
Installing a 7.x Driver

You can install a 7.x driver from the I/O Drivers and OPC Servers CD.
To install a 7.x driver from the Drivers CD:
1. Insert the CD into your CD-ROM drive.

2. When the start screen appears, click the Install Driver button.
3. Select the 7.x GE9 driver and click Install Now.
4. Click I Agree to accept the licensing agreement.
5. Click Next until prompted for the location of FIX or Dynamics on your computer.
6. Verify that the location of FIX or Dynamics is correct and click Next. Otherwise, enter the
correct location.
7. Select Server as the Node Type.
8. Enter the FIX node name of this computer as specified in the System Configuration Utility
(SCU).
9. Enter the name of the folder in the Windows Start menu that you want the driver to be placed
in. By default, the driver and its help file are placed in the FIX or Dynamics folder.
10. Click Finish to install the driver.
Upgrading to GE9 7.x from GE9 7.x

You can upgrade from one version of the GE9 7.x driver to another using the steps provided below.
Before you begin:
1. Create a directory on your hard disk and copy:

a. Your process database file (databasename.PDB).
b. Your GE9 configuration file (filename.GE9).
Typically, the process database resides in your Database path. The GE9
configuration file resides in the default file name path defined in the Power Tool.
2. Save the existing driver configuration file as a Text (*.csv) file. To do this:
a. Select Save As from the File menu in the Power Tool.
b. Select Text Files (*.CSV) from the Save File as Type field.
The Power Tool saves the CSV file in the default file name path.
3. Export the process database as follows:
a. Start Database Builder.
b. Select Export from the Database menu. If you are using FIX32, the exported
database resides in a *.GDB file in the \PDB directory. However, if you are using
iFIX, you can export the database to a CSV file. Regardless of the format, the
exported file resides in the \PDB directory.
4. Rename the existing filename.GE9 and DEFAULT.GE9 files residing in the default file name
path to filename.OLD and DEFAULT.OLD.
27
GE9 OPC Server
Upgrading the GE9 7.x driver:
1. 1. Create a temporary directory on your hard drive, for example, C:\upgrade.

2. 2. Uninstall the existing GE9 driver:
a. Double-click the Add/Remove Programs icon in Control Panel.
b. Locate and highlight the GE9 I/O Server.
c. Click the Add/Remove button to uninstall it.
3. If you are installing a new version from the Driver CD, click the Install Driver button, select
the GE9 7.x driver, and click the Install Now button. Follow the instructions on the screen and
when the installation completes, refer to After Upgrading.
However, if you downloaded a SIM from the GE Fanuc web site, extract your driver files to
the temporary directory:
a. If the downloaded file is a *.EXE file, copy it to the temporary directory, and double
click it to extract the files.
b. If this downloaded file is a *.ZIP file, run WinZip and extract the files to the
directory.
c. If you have individual driver files, copy them to your temporary directory.
4. Install the new version of the GE9 driver from the temporary directory you created:
a. Double-click the Setup.exe icon.
b. Click Next until prompted for the location of FIX or Dynamics on your computer.
c. Verify that the location of FIX or Dynamics is correct and click Next. Otherwise,
enter the correct location.
d. Select Server as the Node Type.
e. Enter the FIX node name of this computer as specified in the System Configuration
Utility (SCU).
f. Enter the name of the folder in the Windows Start menu that you want the GE9
driver to be placed in. By default, the GE9 driver and its help file are placed in the
FIX or Dynamics folder.
g. Click Finish to install the GE9 driver.
After upgrading:
1. Start the new version of the Power Tool.

2. Enter the default configuration file name and verify the default path:
a. Click the Setup button in the Run-time toolbar.
b. Select the Default Path tab.
c. Enter the configuration file’s default name in the field provided.
d. Confirm the default path is correct. If it is not, change it.
3. Select Open from the File menu.
4. Select Text Files (*.CSV) from the List Files of Type field. The previously saved *.CSV file
should appear in the file list.
5. Double-click the CSV file to read your old configuration back into the Power Tool.
28
GE9 OPC Server
6. Select Save As from the File menu.

7. Enter filename.GE9 as the file name.
8. Close the Power Tool and start FIX or iFIX.
Once you import the OPC Server configuration, we recommend that you import your process database
as follows:
1. Save and reload the driver configuration.
2. Start Database Builder and select Reload from the Database menu.
3. Select the local node and double-click the file EMPTY.PDB.
4. Select Import from the Database menu.
5. Select the *.GDB or *.CSV file that you saved before the upgrade. After the import is
complete, a window appears and tells you if there were any import errors. If there were they
will be described in a file named IMPORT.ERR. This file resides in the \PDB directory.
6. Select Save As from the Database menu.
7. Save the database with the name specified in the SCU.
8. Select Reload from the Database menu.
9. Select the local node and double-click the database you just saved.
29
Using the Power Tool
The GE9 I/O Driver Power Tool is your main configuration utility for setting up and maintaining the
GE9 I/O driver. It provides fields for specifying the properties of channels, devices, and datablocks.
Features
The Power Tool provides:
• The Template dialog box for specifying channel, device, and datablock defaults.
• The Setup dialog box for defining the default name and default path for configuration files.
• The Server Connection dialog box for connecting to a remote or local I/O Server.
• The Tree Browser for an overall view of your system configuration.
• A Statistics mode for displaying the statistics of your I/O driver while it is running. Statistics
are provided for all levels: driver, channel, device, and datablock.
• A Configuration mode for displaying and modifying driver, channel, device, and datablock
properties.
Access Methods
From the Windows Start menu:
1. Select Programs.
2. Select FIX, Dynamics, or iFIX from the Programs menu.
3. Select GE9 Power Tool from the context menu.
From FIX Database Builder:
• Select GE9 from the Drivers menu.
From the FIX System Configuration Utility (SCU):
1. Select SCADA from the Configure menu.

2. Double-click your driver from the Configured I/O Drivers list box.
When you first start the Power Tool, the Server Connection dialog box appears. This dialog box lets
you choose the server that the Power Tool communicates with. You can choose either the Local Server
(on your computer) or a Remote Server (on the network).
Once you choose a server, the I/O Driver Power Tool attempts to connect to the server. If the
connection is successful, a message appears telling you that the connection is established. Then the
main window of the Power Tool appears. This window is comprised of:
• The Properties Viewer
• The Menu Bar
31
GE9 OPC Server
By default, the following additional components also appear:

• Tree Browser
• Main Toolbar
• Configuration Toolbar
• Run-time Toolbar
• Status Bar
You can show or hide any of the components by selecting a command from the View menu. You can
also customize the Power Tool’s appearance by dragging the toolbars or the Tree Browser to the
location you want. For example, you can make the toolbars or the Tree Browser float above the Power
Tool by dragging them to the center or the screen. Later, you can dock them or resize them, as needed.
Understanding the Power Tool's Graphic Interface

The following topics discuss the Power Tool's graphic interface.
• Using the Power Tool's Properties Viewer
• Using the Power Tool's Browser
• Using the Power Tool's Menu Bar
• Shortcut Keys
• The Status Bar
• Using the Power Tool's Main Toolbar
• Using the Power Tool's Run-time Toolbar
• Using the Power Tool's Configuration Toolbar
Using the Power Tool’s Properties Viewer

The Properties Viewer displays the statistics or configuration properties of the selected item in the Tree
Browser.
32
GE9 OPC Server
Properties Viewer Displaying Channel Statistics Properties
To display the configuration properties for a driver, channel, device, or datablock:
• Select an item in the Tree Browser and click the Configuration button in the Run-time toolbar.
To modify an item’s configuration:
1. Select the item you want to modify in the Tree Browser.

2. Click the Configuration button in the Run-time toolbar.
3. Modify the item’s properties in the fields provided.
To view statistics for a driver, channel, device, or datablock:
• Select an item in the Tree Browser and click the Statistics button in the Run-time toolbar.
Using the Power Tool’s Browser

The Tree Browser displays a hierarchical list of the I/O driver and its channels, devices, and
datablocks. The I/O driver appears at the top of the tree.
33
GE9 OPC Server
Power Tool Tree Browser
When you select an item in the Tree Browser, its properties display in the Properties Viewer. You can
choose to view the item's configuration or statistics properties by clicking buttons on the Run-time
toolbar.
Changing Items in the Tree Browser
When you add or modify channels, devices, or datablocks in the Power Tool or in FIX Database
Builder, changes are made immediately to the I/O Server. Changes you make to the driver
configuration while working with the I/O Driver Power Tool automatically display in the Tree
Browser. For changes from Database Builder to take effect, the Auto Create option must be enabled.
Refreshing the Tree Browser
To view changes made from another client application (such as FIX Database Builder, another I/O
Driver Power Tool accessing the server, or a custom client application accessing the server), refresh
the Tree Browser display by selecting an item in the Tree Browser and pressing the F5 key.
Collapsing and Expanding the Tree Browser
You can collapse or expand the tree under an item by double-clicking it. You can also use the right
arrow key to expand an item and the left arrow key to collapse it.
Navigating in the Tree Browser
Navigating through the Tree Browser can be done by selecting items with a mouse or by using the
keyboard. Use the up or left arrow keys to move up in the Tree Browser. Similarly, use the down or
right arrow keys to move down in the Tree Browser. You can also press a letter key to jump to the
nearest item that begins with that letter.
Additional Tree Browser Features
Connection lines show the relationship between channels, devices, and datablocks by displaying which
devices are on a channel and which datablocks belong to a device. The plus and minus buttons indicate
whether items are fully expanded or collapsed. The plus button shows the item is collapsed and the
minus buttons indicates that the item is expanded. For example, a channel with a plus sign next to it
means that there are devices and possibly datablocks configured on that channel.
Using the Power Tool's Menu Bar

The Power Tool menu bar includes a title bar, a Minimize button, a Maximize button, a Control-menu
box, and menus you can use to configure the driver. The menu bar is displayed at the top of the screen
but you can resize it and drag it to another location.
34
GE9 OPC Server
The Power Tool has the following menus:

• File
• Edit
• View
• Display Mode
• Options
• Help
To open a menu and display its commands:
• Click the menu name.
To choose a command:
• Open the command's menu and click the command name or press the command’s shortcut
keys. You can find the shortcut keys for a command next to the command on its pull-down
menu. For example, select the File menu and note that the shortcut key for the New command
is Ctrl + N.
Using the Display Mode Menu
The commands in the Display Mode menu let you display the driver’s configuration or statistics in the
Properties Viewer.
Configuration Mode
Displays the properties of the item selected in the Power Tool’s browser. These properties appear in
the Properties Viewer.
Statistics Mode
Displays the statistics of the item selected in the Power Tool’s browser. The statistics appear in the
Properties Viewer and are read-only.
Using the Edit Menu
The commands that appear in the Edit menu are for creating and modifying driver configuration files.
These commands correspond with the buttons on the Power Tool’s Configuration Toolbar.
Add Channel
Lets you enter a new channel configuration.
Add Device
Lets you enter a new device configuration.
35
GE9 OPC Server
Add Datablock
Lets you enter a new datablock configuration.
Delete
Deletes the channel, device, or datablock currently selected in the Tree Browser. When you delete an
item, all of its associated items are deleted. For example, if you delete a channel, all devices and
datablocks on that channel are deleted.
Using the File Menu
The following commands appear on the File menu.
New
Lets you make a new driver configuration file.

Keyboard shortcut: Ctrl + N.
Open
Lets you open an existing driver configuration file. You can select .GE9 or .CSV file types.
Keyboard shortcut: Ctrl + O.
Save
Saves the current driver configuration file to the default path for configuration files with the name you
specify. The default path for configuration files is the same path where you installed the server. You
can change the default path by entering a new location. Refer to Setting Defaults for I/O Driver
Configuration File Name and Path to learn how to configure the default path for the Power Tool.
If you save a new driver configuration file, the Save As dialog box prompts you to enter a name for
your driver configuration file.
Keyboard shortcut: Ctrl + S.
Save As
Lets you enter a new name and file type for the current driver configuration.
Save As Dialog Box Options
Option Description
Save In field Lets you select the directory that you want to store the file in.
36
GE9 OPC Server
Option Description
File Name field Lets you save a file with a new name, or in a different location, by entering a
new file name in the File Name field or by selecting a new directory in the
Save In list. To save a file with an existing file name, select the name in the
list or enter the current name.
Save as Type Lets you specify the type of file you want to save the configuration as:
field
• A configuration file – Lets you save the file in the format that the
driver uses to communicate with the process hardware.
• A comma separated value file (.CSV) – Lets you save the file as a
text file. You can open these files in a text editor and use them to
document your driver configurations. You can also modify .CSV
files in a text editor, open them in the Power Tool, and save them as
configuration files. The delimiters for .CSV files conform to
national standards. For example, in the United States, .CSV file
delimiters are commas. In France, .CSV file delimiters are
semicolons. Saving a configuration as a .CSV file is sometimes
referred to as exporting the driver configuration.
Refer to Using I/O Driver Report Files for details on how to use the different
file types most effectively.
Save button
Saves the file under the specified name.
Cancel button
Closes the dialog box without saving the file.
Exit
Exits the Power Tool.
Using the Help Menu
The commands in the Help menu provide access to the Power Tool’s online help and version number.
Help Topics
Displays the GE9 Power Tool online help.
About
Displays the Power Tool’s version number.
37
GE9 OPC Server
Using the Options Menu
The commands in the Options menu let you access specific Power Tool options.
Reset Counters
Resets the statistics of the item currently selected in the Tree Browser. This command is only
accessible when the Power Tool is in Statistics mode. To enable Statistics mode, click the Statistics
button from the Run-time toolbar.
Templates
Lets you enter defaults for the driver’s channels, devices, and datablocks.
Setup
Lets you select the statistics refresh rate, enter defaults for the I/O driver configuration file name and
path, and make advanced settings.
OLE Server
Lets you select a local or remote OLE server.
Data Scope
Displays the data scope for this server. Any objects that have the data scope enabled send messages to
the Data scope window.
Data Scope
Displays the data scope for this server. Any objects that have the data scope enabled send messages to
the data scope window.
To enable the data scope for an object:
1. Right-click an object in the Tree Browser.

To print data from the data scope:
1. Click the Pause button on the Datascope toolbar.

2. Press Alt + Shift + Print Scrn to copy the information on the screen to your computer’s
clipboard.
3. Start any graphics program, such as Microsoft Paint or Paint Shop Pro.
4. Select Paste from the Edit menu to copy the clipboard into the graphics program.
5. Select Print from the File menu.
The data scope is a troubleshooting utility. Do not leave it running during production.
38
GE9 OPC Server
Using the View Menu
The commands in the View menu let you customize the Power Tool’s appearance. If a check mark
appears next to a command, the item displays; otherwise, the item is hidden.
Tree Browser
Shows or hides the Tree Browser.
Main Toolbar
Shows or hides the Main toolbar.
Run-Time Toolbar
Shows or hides the Run-time toolbar.
Configuration Toolbar
Shows or hides the Configuration toolbar.
Status Bar
Shows or hides the status bar.
Using Shortcut Keys

The following is a list of shortcut keys for working with the I/O Driver Power Tool:
Shortcut Key Description
F5 key Refreshes the Tree Browser.
Ctrl + N Opens a new I/O driver configuration file.
Ctrl + O Lets you open an existing file.
Ctrl + S Saves the current file.
Alt + Shift +S Opens and closes the server window when an item in the Tree Browser is
selected. Use the server window for troubleshooting. When you are not
debugging a problem, leave the server window closed.
The Status Bar

Displays Power Tool status messages. It is located under the Properties Viewer.
39
GE9 OPC Server
Example
Using the Power Tool’s Main Toolbar

The Power Tool’s Main toolbar is shown below:
The Main toolbar buttons are shortcuts to some commonly-used menu items.
Icon Description
New – Creates a new I/O driver configuration file.
Open – Opens an existing I/O driver configuration file.
Save – Saves the current I/O driver configuration file. If the current
configuration is new, the Save As dialog box appears with fields for naming
the file and choosing a file type.
Save As – Saves the current configuration file:

• With a different file name.
• As a configuration file.
• As a comma separated value (CSV) file.
Help Topics – Displays the GE9 I/O driver online help.
Using the Power Tool’s Run-time Toolbar

The Run-time toolbar is shown below:
The Run-time toolbar contains buttons that are shortcuts to dialog boxes for viewing driver
configurations and statistics.
Icon Description
Start – Starts the driver. Enabled only when the driver is not running.
40
GE9 OPC Server
Icon Description
Stop – Stops the driver. Enabled only when the driver is running.
Configuration – Displays the configuration of the item selected in the Power

Tool’s browser. These properties appear in the Properties Viewer.
Statistics – Displays statistics of the item selected in the Power Tool’s

browser. The statistics appear in the Properties Viewer and are read-only.
Reset – Resets the statistics of the item currently selected in the Tree
Browser. This button is only accessible when the Power Tool is in Statistics
mode. Click the Statistics button shown above to enable Statistics mode.
Template – Lets you enter defaults for the driver and its channels, devices,
and data blocks.
Setup – Lets you select the statistics refresh rate, enter defaults for the I/O
driver configuration file name and path, and make advanced settings.
OLE Server – Lets you select an OLE server.
Data Scope – Displays the data scope for this server. Any objects that have
the data scope enabled send messages to this window.
To enable the data scope for an object:
1. Right-click an object in the Tree Browser.
Using the Power Tool’s Configuration Toolbar

The Configuration toolbar is shown below:
The Configuration toolbar buttons are shortcuts to the driver configuration dialog boxes.
Icon Description
Add Channel – Lets you enter a new channel and its properties.
41
GE9 OPC Server
Icon Description
Add Device – Lets you enter a new device and its properties.
Add Datablock – Lets you enter a new datablock and its properties.
Delete – Deletes the channel, device, or datablock currently selected in the

Tree Browser.
Setting Up the Power Tool's Environment

You can set up the Power Tool’s environment by displaying the Setup dialog box and completing each
tab. The Setup dialog box lets you do the following:
• Set the statistics refresh rate.
• Set the default configuration file name and default path for the configuration file.
• Make advanced settings for your I/O driver.
To open the Setup dialog box:
• Click the Setup button in the Run-time toolbar.
Setting the Statistics Refresh Rate
To set the refresh rate:

2. Select the Display Setup tab.
3. Enter the refresh rate in the field provided.
IMPORTANT: The Power Tool reads the refresh rate whenever you switch into Statistics mode.
Consequently, if you change the refresh rate while in Statistics mode, your changes do not take effect
immediately. In order for the new refresh rate to take effect, you must switch into Configuration mode
and then back to Statistics mode.
42
GE9 OPC Server
Setting Defaults for I/O Driver Configuration File Name and Path
The default path for the configuration file is the same path where you installed the I/O Server. The
GE9 driver requires you to specify the default path and the name when you automatically start the
driver.
To set the default configuration file name and change the default path:

2. Select the Default Path tab.
3. Enter the configuration file’s default name and default path in the fields provided.
NOTES:
• A configuration file named nodename.GE9 is saved in the root Dynamics directory when you
install the driver. If you are using FIX, the file resides in the Database path (C:\FIX32\PDB,
by default). Do not delete this file. FIX and iFIX use this file to load the driver.
• If you change the name of your SCADA server after installing the GE9 driver, FIX cannot
automatically start the driver because the name of the node does not match the name of the
configuration file. To correct this, rename the configuration file to match the name of your
SCADA server. For example, if you change the name of the SCADA server from SCADA1 to
SCADA9, rename the configuration file from SCADA1.GE9 to SCADA9.GE9.
Making Advanced Settings

You can make more detailed settings for your driver using the Advanced tab in the Setup dialog box.
CAUTION: Advanced settings are for fine-tuning your driver and should not be changed unless you
have an intimate knowledge of how the driver operates and know that you need to make some
adjustments.
To make advanced driver settings:
1. Click the Setup button, in the Run-time toolbar.

2. Select the Advanced tab. The Advanced fields display as shown below.
43
GE9 OPC Server
3. Complete the Advanced fields by making selections for the following fields.
Simulation Mode Auto Start
Auto Create Simultaneous Messages per Device
Connection Timeout
Fields and Check Boxes

When setting up the Power Tool's environment, you can use the following fields, check boxes and
buttons:
• Refresh Rate Field
• Auto Create Off Button
• Auto Create On Button
• Auto Start Off Button
• Auto Start On Button
• Connection Timeout Field
• Simulation Mode On Button
• Simulation Mode Off Button
• Simultaneous Messages per Device Field
Refresh Rate Field
Specifies the number of milliseconds that the I/O driver, channel, device, and datablock statistics
update.
44
GE9 OPC Server
The Power Tool reads the refresh rate whenever you switch into Statistics mode. Consequently, if you
change the refresh rate while in Statistics mode, your changes do not take effect immediately. In order
for the new refresh rate to take effect, you must switch into Configuration mode and then back to
Statistics mode.
NOTE: If you specify a very fast refresh rate (for example, every 100 milliseconds), other driver tasks
slow down as the driver works to constantly refresh statistics.
Auto Create Off Button
Prohibits you from creating datablocks automatically from within FIX. If this option is selected, you
must use the Power Tool to create datablocks.
Default Value
On
NOTE: Whenever you enable or disable the Auto Create option, close all remote connections to the
I/O Server and restart the Power Tool in order for your changes to take effect.
Auto Create On Button
Lets you create datablocks automatically from a client application, such as Database Builder. When the
client application attempts to access a non-existent datablock, the current datablock expands, if
possible, or the driver creates a new datablock.
Default Value
On
NOTE: Whenever you enable or disable the Auto Create option, close all remote connections to the
I/O Server and restart the Power Tool in order for your changes to take effect.
Auto Start Off Button
Prohibits the driver from collecting data automatically. As a result, you must start the driver yourself,
or use FIX to start it for you.
NOTE: Whenever you enable or disable the Auto Start option, close all remote connections to the I/O
Auto Start On Button
Lets the driver automatically start polling the process hardware for data. When you set up the driver to
run as a service, this option lets the driver collect data immediately on start-up.
NOTE: Whenever you enable or disable the Auto Start option, close all remote connections to the I/O
Connection Timeout Field
Specifies a connection timeout period in milliseconds that is used by the GE9 driver to determine the
timeout period during the connection phase with the GE 90 Series of PLC hardware. This timeout
value is applicable to the SRTP connect and Establish Session commands sent to the PLC to
successfully connect with the PLC.
45
GE9 OPC Server
If the PLC connects successfully before the timeout period expires, the driver continues sending
Read/Write messages and will not wait for the timeout period to expire. If the PLC responds with an
error message, the driver will take the appropriate action in response to the error without waiting for
the timeout period to expire.
Valid Entries
100 ms to 600000 ms (10 minutes)
Default Value
1000 ms (1 second)
Simulation Mode On Button
Enables simulation mode for the I/O driver. In simulation mode, all writes go directly to the datablocks
instead of the process hardware.
Default Value
Off
Simulation Mode Off Button
Disables simulation mode for the I/O driver causing all writes go directly to the process hardware.
Default Value
Off
Simultaneous Messages per Device Field
Specifies the maximum number of messages sent to each configured device at one time. The messages
sent to each device are stored in the PLC’s memory buffer.
By sending multiple messages to a PLC, you can improve performance when the PLC is very busy
because it is more efficient for the process hardware to access the messages from its memory buffer
than to wait for new requests from the network.
Valid Entries
1 to 4
46
GE9 OPC Server
Default Value
1
NOTE: Whenever you change the value in the Simultaneous Messages per Device field, stop and
restart the driver in order for your changes to take effect.
47
Setting Up the GE9 I/O Driver Server
Connection
The Power Tool is a client of the GE9 I/O Server. The Server maintains the driver's channel, device,
and datablock objects and performs all required functions for communicating with the process
hardware. The Power Tool accesses the Server and lets you view and modify channel, device, and
datablock properties.
The GE9 I/O Server Connection dialog box displays when you first start the Power Tool. This dialog
box lets you choose whether to set up the Power Tool to communicate with a Local I/O Server (on
your computer) or a Remote I/O Server (a computer on the network). If you choose a remote I/O
Server, you must enter or select the remote machine name or address.
To change the GE9 I/O Server connection:
• You can display the GE9 I/O Driver Server Connection dialog box and change the settings at
any time by clicking the GE9 I/O Server button in the Power Tool's Run-time toolbar.
To connect to the server on the local machine:
1. Start the GE9 I/O Driver Power Tool or click the Server button in the GE9 I/O Driver Power
Tool.
2. Select the Use Local Server option and click Connect.
The Power Tool attempts to connect to the local server. If the connection is successful, the
Connection dialog displays the message Connection Established and then the main
window of the Power Tool displays. If the connection is not successful, the Connection dialog
boxes displays the message Connection Not Established and you receive the following
message:
Connection to the selected server has failed. Do you want to select
another server?
3. Click Yes if you want to try connecting to a remote server. If you cannot connect to the local
server, there is a problem with the server start-up. Refer to Using the Event Viewer for details
on how to display any errors that the server may have generated.
To connect the server on a remote machine:
1. Start the GE9 I/O Driver Power Tool or click the Server button in the GE9 I/O Driver Power
Tool.
2. Select the Use Remote Server option and enter the remote machine name or TCP/IP address
in the Remote Machine Name or TCP/IP Address field.
You must enter the machine name or address exactly. If you do not know the exact machine
name, select it using the Network list box. If the connection is successful, the Connection
dialog displays the message Connection Established and then the main window of the
Power Tool displays. If the connection is not successful, the Connection dialog boxes displays
the message Connection Not Established and you receive the following message:
Connection to the selected server has failed. Do you want to select
49
GE9 OPC Server
another server?
3. Click Yes, if you want to try another server. If you cannot connect to the machine that the
server is on, you may not have an account to that machine or your DCOM settings may be
incorrect. . Refer to How do I Set up Security for using the I/O Server Remotely for more
information.
Use the Show this Dialog on Startup check box, to select whether to display the GE9 I/O Driver Server
dialog box every time you start the driver.

When setting up the GE9 I/O Driver Server Connections, you will use the following fields, check
boxes and buttons:
• Network List Box
• Remote Machine Name or TCP/IP Address Field
• Show This Dialog On Startup Check Box
• Use Local Server Button
• Use Remote Server Button
Network List Box

Displays all the computers on the local network. These nodes are not all servers. You should know
which computer the GE9 I/O Server that you want to connect to resides on.
Remote Machine Name or TCP/IP Address Field

Displays the remote server's computer name or TCP/IP address. If you know the name or address of
the remote server, you can enter it directly in the field. Otherwise, you can browse the network using
the Network list box and select the appropriate computer.
Show This Dialog on Startup Check Box

Lets you display the I/O Driver Server Connection dialog box when you start the driver. If you select
this check box, the I/O Driver Server Connection dialog box displays ever time you start the driver,
letting you make changes to your driver connection settings.
If you clear the check box, the I/O Driver Server Connection dialog box does not display. If you plan
to always use the same I/O Server, clearing the check box saves you from having to click Connect
every time you start the driver.
Use Local Server Button

Lets you connect to the GE9 I/O Server on the local node.
Use Remote Server Button

Lets you connect to the GE9 I/O Server on a remote node. You should know the name of the computer
that the GE9 I/O Server resides on.
50
GE9 OPC Server
To connect to a remote machine, do one of the following tasks:
• Enter the remote server’s name in the Remote Machine Name or TCP/IP Address field.
• Enter the remote server’s TCP/IP address in the Remote Machine Name or TCP/IP Address
field.
• Select a remote server from the Network list box. The server’s name automatically appears in
the Remote Machine Name or TCP/IP Address field.
The remote server name may not be the same as its FIX node name.
51
Setting the I/O Server for Automatic
Connection
To set your I/O Driver Power Tool to connect automatically to the I/O Server on either
a local or remote machine:
1. From the Windows Explorer, open your FIX folder, typically C:\FIX32, and select
GE9DIDW.EXE.
2. Create a shortcut by right-clicking the mouse and selecting Create Shortcut from the menu
displayed.
3. Select the GE9 Shortcut to the Power Tool.
4. Right-click the mouse and select Properties from the menu displayed.
5. Select the Shortcut tab.
6. In the Target field, add one of the following command line parameters after GE9didw.exe as
shown in the examples:
Remote Connection Example
/N remote_machine_name GE9DIDW.EXE/ N Jake
/N remote_ip_address GE9DIDW.EXE/ N 199.103.251.114
Local Connection Example
/L GE9DIDW.EXE/ L
This setup suppresses the I/O Driver Server Connection dialog box on Power Tool start-up. This is a
good practice if you plan to always use the same server on the same computer.
53
Configuring Channels, Devices and
Datablocks
This section describes how to configure channels, devices and datablocks. The following topics are
discussed:
• Choosing a Method for Configuring Your Driver
• Configuring the I/O Driver with the Power Tool
• Creating Datablocks Inside FIX Applications
• Using I/O Driver Report Files
Choosing a Method for Configuring Your Driver

You can configure the GE9 I/O driver in several ways. The best method for you depends on how you
decide to configure your process control system. The following table lists the driver configuration
methods to choose from:
Method When to Use
Using the Power If you are familiar with your process hardware and want to make a detailed
Tool configuration.
Creating If you are using FIX for process control and you know:
Datablocks from
• The names of the devices you want the driver to access.
FIX Database
Builder • The registers and addresses in the devices that you want to access.
Using a Visual If you are using a custom automation application built with a scripting
Basic Client language such as Visual Basic to configure the driver and access data.
Application
Configuring the I/O Driver with the Power Tool
To configure the GE9 I/O driver with the Power Tool:
1. Click the Add Channel button on the Configuration toolbar to add a channel to the Tree
Browser.
2. Click the Add Device button to add a device.
3. Enter the IP address of the device you want to communicate with.
4. Click the Add Datablock button to add a datablock.
55
GE9 OPC Server
5. Add channels, devices, and datablocks as needed.

6. Modify the fields in the Properties Viewer as needed.
To modify the fields in the Properties Viewer:
1. Select a channel, device, or datablock from the Tree Browser. The fields for the selected item
appear in the Properties Viewer.
2. Edit the fields you want to change.
Channels
The following topics, which explain how to configure channels, are discussed:
• Adding and Modifying Channels
• Fields and Check Boxes
Adding and Modifying Channels
To add a new channel to your driver configuration:
1. Click the Add Channel button on the Configuration toolbar. The new channel appears in the
Tree Browser and the fields for entering channel properties appear in the Properties Viewer.
2. Enter the properties for the new channel. Edits to a field do not take effect until you remove
the focus (the cursor) from the field.
3. Select the Enable check box to enable communication for the new channel.
To modify an existing channel:
1. Select the channel you want to modify from the Tree Browser.
2. Edit the channel’s fields as needed. If the Enable check box is selected, the new channel
settings take effect immediately once you remove focus (the cursor) from the current field.
When configuring channels, you will use the following fields and check boxes:
• Channel Description Field
• Channel Enable Check Box
• Channel Name Field
Channel Description Field
Lets you enter text about the selected channel. Entries in this field can be very helpful when you go
back to look at old configuration or report files, or when you need to modify an existing configuration.
The more detailed and specific the information you enter in this field, the easier it is to identify the
channel.
56
GE9 OPC Server
Valid Entries
Up to 40 alphanumeric characters and symbols.
Channel Enable Check Box
Enables the driver to poll the channel when you select the check box. If you clear the check box, the
driver does not poll the selected channel or any of the channel’s devices or datablocks.
Channel Name Field
Specifies the name of the selected channel.
Valid Entries
Up to 12 alphanumeric characters, including underscores ( _ ) and hyphens ( - ).
Devices
The following topics, which explain how to configure devices, are discussed:
• Adding and Modifying Devices
• Setting up a Device IP Address
• Setting Device Timing Properties: Reply Timeout, Retries, and Delay Time
Adding and Modifying Devices
To add a new device to your driver configuration:
1. From the Tree Browser, select the channel you want to add the device to.
2. Click the Add Device button on the Configuration toolbar. The new device appears in the
Tree Browser and the fields for entering device properties appear in the Properties Viewer.
3. Enter the properties for the new device. Edits to a field do not take effect until you remove the
focus (the cursor) from the field.
4. Select the Enable check box to enable communication for the new device.
To modify an existing device:
1. Select the device you want to modify from the Tree Browser.
2. Edit the device’s fields as needed. The device updates automatically once you remove the
focus (the cursor) from the current field.
Setting up a Device IP Address
You need to configure the I/O driver with your device’s IP address. You can enter the primary device’s
IP address in the Primary IP Address field and the back-up device’s IP address in the Backup IP
Address field.
57
GE9 OPC Server
When the I/O driver starts, it attempts to establish communications with the specified primary device.
If it successfully establishes communications with this device, the driver polls for data according to
your datablock configuration. If communication with the primary device fails, the driver switches to
the specified back-up device. If the driver successfully establishes communications, it polls data from
this device. However, the back-up device cannot communicate or is unavailable, the driver switches
back to the primary device. This process of switching between devices continues until the driver
receives a response from one of the specified devices.
NOTE: If you do not have a back-up device, leave the Backup IP Address Field blank. This
configuration prevents the driver from switching the nonexistent device and avoids unnecessary
delays.
You may have to add your each device’s IP address to your computer’s HOSTS file for proper
communications.
Setting Device Timing Properties: Reply Timeout, Retry, and Delay Time
Reply Timeout, Retries, and Delay Time are the timing properties of the driver and are set for each
device.
The timing sequence is as follows:
1. The I/O driver sends a message to the process hardware and waits the length of time specified
in the Reply Timeout field for a response.
2. If the device does not respond, the driver re-sends the message for the number of times
specified in the Retries field.
3. The driver marks the datablock as failed after all retries have been sent and the device has not
responded.
a. If a back-up device is specified, the driver immediately switches devices, waits the
length of time specified in the Delay Time field, and sends the message to the
datablock on the back-up device. The message is sent once. If the back-up device
does not respond, the driver switches back to the primary device and sends the
message again. This cycle repeats until one of the devices responds.
b. If a back-up device is not specified, the driver waits the Delay Time and re-initiates
the polling process with the selected device.
4. The device may have multiple datablocks. In this situation, the driver uses its QuickFail logic
and only performs one cycle through the Timeout, Retries, and Delay process for the
messages currently in the Read queue. It then marks the datablock and all subsequent
datablocks on that device as failed and moves on to the next device. The next time the driver
attempts to send the message to the failed device, it ignores the Retries and only makes one
attempt. If the attempt is successful, the driver recovers all datablocks on the device and
marks them ready for messages.
By using QuickFail, the driver saves time and bypasses the problem device, thereby increasing its
efficiency.
Example
Reply Timeout = 05 (5 seconds)

Retries = 5
Delay Time = 5:00 (5 minutes)
Backup Device = none
58
GE9 OPC Server
The driver attempts to send a message to the process hardware. After 5 seconds, the device still has not
responded, so the driver re-sends the message.
The driver tries to send the message 6 times (the first time and then the 5 retries) with 5-second
intervals between each attempt.
Each attempt fails; consequently, the driver marks the datablock as failed. If the driver has messages
for other datablocks on the same device, it sends them only once without retries.
The driver waits 5 minutes before attempting to re-establish communication with the failed device.
When configuring devices, you will use the following fields and check boxes:
• Backup Device Delay Time Field
• Backup Device Reply Timeout Field
• Backup Device Retries Field
• Backup IP Address Field
• Device Description Field
• Device Enable Check Box
• Device Name Field
• Delay Time Field
• Reply Timeout Field
• Retries Field
• Primary IP Address Field
Backup Device Delay Time Field
Specifies how long the I/O driver waits before attempting to communicate with a backup device. The
driver waits the delay time after all retries for the backup device have failed.
Valid Entries
Accepts the time format: days:hours:minutes:seconds up to a maximum of 6:23:59:59.
Example
To specify a delay time of... Enter
1 second 1
1 minute 1:00
1 hour and 30 minutes 1:30:00
59
GE9 OPC Server
2 days 2:00:00:00
Backup Device Reply Timeout Field
Specifies how long the I/O driver waits for a response from the selected back-up device. Typically, the
back-up device is used when communication with the primary device fails.
Valid Entries
Example
To specify a timeout of... Enter
1 second 1
1 minute 1:00
2 days 2:00:00:00
Backup Device Retries Field
Specifies how many times the driver re-sends a failed message to the back-up device before marking a
datablock as failed and initiating the Delay Time.
Valid Entries
0 to 9
Backup IP Address Field
Specifies the IP address of the GE Fanuc Series 90 Ethernet Interface module that you want to use as
your back-up device. The driver switches to this device if the primary device cannot communicate or
becomes unavailable.
The back-up IP address you specify must be different from the primary IP address and must match the
IP address configured for your back-up GE Fanuc Series 90 Ethernet Interface module.
Example
3.0.0.101
60
GE9 OPC Server
When the driver starts, it will attempt to establish connection with the GE Fanuc Series 90 Ethernet
Interface at the specified primary IP address. If the driver successfully establishes a connection with
the device at this address, it polls for data from the device according to the datablock configuration. If
the driver fails to establish communications with the device, it switches to the back-up device. If driver
cannot communicate with the primary or the back-up device you specified, ping your hardware to
ensure they are available and communicating with the network.
NOTE: For proper communications, you may have to add the primary and back-up device’s IP
address to the HOSTS file located in the \WINNT\SYSTEM32\DRIVERS\ETC subdirectory.
Device Description Field
Contains text about the selected device. Entries in this field can be very helpful when you go back to
look at old configuration or report files, or when you need to modify an existing configuration that you
did not create. The more detailed and specific the information you enter in this field, the easier it will
be to identify the device at a later date.
Valid Entries
Device Enable Check Box
Enables the driver to poll the selected device when you select this check box. If you clear the check
box, the driver does not poll the selected device or any of its datablocks.
You may want to disable one or more devices in the following situations:
• You are swapping hardware for repair or maintenance and do not want to display errors.
• You do not need to collect data from all your devices and you want to reduce the
communications load.
• You want to isolate a device for debugging.
Device Name Field
Specifies the name of the selected device. Any application requesting data from the I/O driver uses this
name to access points in the device’s memory. Each device that the driver communicates with should
have a unique device name regardless of the device’s channel.
Valid Entries
Up to 12 alphanumeric characters including underscores ( _ ) and hyphens ( - ).
Delay Time Field
Specifies how long the I/O driver waits before attempting to communicate with a device. The driver
waits the delay time after all retries have failed.
Valid Entries
61
GE9 OPC Server
Example
1 second 1
1 minute 1:00
2 days 2:00:00:00
Reply Timeout Field
Specifies how long the I/O driver waits for a response from the selected device.
Valid Entries
Example
To specify a timeout of... Enter
1 second 1
1 minute 1:00
2 days 2:00:00:00
Retries Field
Specifies how many times the driver re-sends a failed message to the device before marking a
datablock as failed and initiating the Delay Time.
Valid Entries
0 to 9
Primary IP Address Field
Specifies the IP address of the GE Fanuc Series 90 Ethernet Interface module that you want to use as
your primary device. To ensure the driver communicates property, make sure the primary IP address
62
GE9 OPC Server
you enter matches the IP address configured for the GE Fanuc Series 90 Ethernet Interface module.
Example
3.0.0.1
When the driver starts, it will attempt to establish connection with the GE Fanuc Series 90 Ethernet
Interface at the primary IP address you specify. If the driver successfully establishes a connection with
the device at this address, it polls for data from the device according to the datablock configuration. If
the driver fails to establish communications with the device, it switches to the back-up device (if
configured). If driver cannot communicate with the device you specified, ping your hardware to ensure
it is available and communicating with the network.
NOTE: For proper communications, you may have to add the device’s IP address to the HOSTS file
located in the \WINNT\SYSTEM32\DRIVERS\ETC subdirectory.
Datablocks
The following topics, which explain how to configure datablocks, are discussed:
• Adding and Modifying Datablocks
• Setting Datablock Address Properties: Start, End, and Length
• Setting Datablock Timing Properties: Rate, Phase, and Access Time
• Using Primary and Secondary Poll Rates with Access Time
• Using Phasing with Poll Rates
• Creating Datablocks with the Power Tool
Adding and Modifying Datablocks
To add a new datablock to your driver configuration:
1. From the Tree Browser, select the device you want to add a datablock to.
2. Click the Add Datablock button on the Configuration toolbar. The new datablock appears in
the Tree Browser and the fields for entering datablock properties appear in the Properties
Viewer.
3. Enter the properties for the new datablock. Edits to a field do not take effect until you remove
the focus (the cursor) from the field.
4. Select the Enable check box to enable communication for the new datablock.
To modify an existing datablock:
1. Select the datablock you want to modify from the Tree Browser.
2. Edit the datablock’s fields as needed. If the Enable check box is selected, your changes take
effect as soon as you remove focus from the field.
Setting Datablock Address Properties: Start, End, and Length
The Starting Address, Ending Address, and Address Length fields define the memory location in the
63
GE9 OPC Server
device that the datablock represents.

You must always enter a starting address. This is the point in the device that the datablock starts from.
You can then enter either an ending address or an address length to complete the entire block.
Example
You want to create a datablock named DATABLOCK-C that starts at address R5 and has a length of 8.
To do this, enter R5 in the Starting Address field and 8 in the Address Length field. The Power Tool
automatically completes the Ending Address field with the value R12.
DATABLOCK-C uses the following location in the device:
Memory Type %R
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18
1920 IIIIII IIIIII IIIIII IIIIII IIIIII IIIIII IIIIII IIIIII
Valid Datablock Addresses
Memory Description Address Maximum Example

Type Range Length
R Registers 1-65000 690 R1
AI Analog Inputs 1-65000 690 AI1
AQ Analog Outputs 1-65000 690 AQ1
I Discrete Inputs 1-65000 11024 bits I1
Q Discrete Outputs 1-65000 11024 bits Q1
M Internal Coils 1-65000 11024 bits M1
T Temporary Coils 1-65000 11024 bits T1
G* Genius Seamless 1-65000 7680 bits G1
S System Fault 1-65000 11024 bits S1

(Read Only)
SA Special Contacts 1-65000 11024 bits SA1

A
64
GE9 OPC Server
Memory Description Address Maximum Example

Type Range Length
SB Special Contacts B 1-65000 11024 bits SB1
SC Special Contacts C 1-65000 11024 bits SC1
The driver allows you to enter any address within the range as mentioned above. It is your
responsibility to verify that the range specified is present in the process controller.
*The Series 90-70 contains only one data space for all of the global data references (%G, %GA, %GB,
%GC, %GD, and %GE). Internal memory for this data is 7680 bits long. Your programming software
provides a subdivided representation by using %G, %GA, %GB, %GC, %GD, and %GE prefixes-
allowing each of these prefixes to be used with bit offsets in the range 1-1280. Your programming
software interprets the requested global reference type (%G, %GA, %GB, %GC, %GD, or %GE) and
converts it to the %G memory type and correct bit offset for use by the process hardware.
** %W addressing is not supported for PACSystems.
While a Series 90-70 understands global data references, the 7.x driver does not. Consequently to
access global memory, create datablocks with a maximum length of 1280 up to the address G7680.
Example
The following datablock can access all the available global memory in a Series 90-70.
Datablock Address Range
%G G1 to G1280
%GA G1281 to 2560
%GB G2561 to G3840
%GC G3841 to G5120
%GD G5121 to G6400
%GE G6401 to G7680
Setting Datablock Timing Properties: Rate, Phase, and Access Time
The Primary Rate, Secondary Rate, Phase, and Access Time fields determine the timing of the driver's
polling process. Polling is the process of sending or receiving messages between the driver and a
specific datablock. The timing sequence works as follows:
1. The driver polls the datablock at the specified primary poll rate. For example, if you enter 2
seconds in the Primary Rate field, the driver polls for data every 2 seconds.
65
GE9 OPC Server
2. The process control software no longer requests data from the datablock. The driver continues
polling at the primary poll rate until the access time expires.
a. If the process control software makes a request on the same datablock before the
access time expires, the access time resets and the driver continues polling at the
primary poll rate.
b. If the access time expires, the driver starts polling the datablock at the secondary poll
rate. To maximize the efficiency of the driver, specify a secondary poll rate that is
longer than the primary poll rate. This configuration ensures that the driver polls the
datablock at a slower rate when there are no requests.
c. If the process control software stops its request, the access time expires, and you do
not specify a secondary poll rate, the driver stops polling the datablock.
d. When the process control software requests data from the datablock again, the access
time resets and the driver polls at the primary poll rate.
Refer to Using Primary and Secondary Poll Rates with Access Time for examples of primary and
secondary poll rates with access times.
Typically, you phase datablocks when you are collecting information from many points on a single
device. Phasing means staggering the first time at which the driver polls its datablocks. When the
phase time expires, the driver resumes reading its datablocks at the specified primary or secondary poll
rate. Refer to Using Phasing with Poll Rates for an example of phasing datablocks.
Using Primary and Secondary Poll Rates with Access Time
Below practical examples for combining your primary poll rates, secondary poll rates, and access times
are provided to help you configure your datablocks.
Example 1
PollRec1
Primary Poll Rate = 10 seconds
Secondary Poll Rate = Disabled
Access Time = 5 minutes
In this datablock, when the access time expires, the driver attempts to poll with the secondary poll rate
then stops because this poll rate is disabled.
Example 2
PollRec2
Secondary Poll Rate = 1 minute
Access Time = 5 minutes
In PollRec2, when the access time expires, the driver switches to the secondary poll rate and then polls
the datablock every minute.
Example 3
PollRec3
66
GE9 OPC Server

Access Time = Disabled
The driver always polls PollRec3 at 10 seconds with this configuration because the access time is
disabled.
Example 4
PollRec4
Primary Poll Rate = Disabled
Access Time = Disabled
The driver does not read messages from PollRec4 on the device. This is the configuration for a write-
only datablock.
Using Phasing with Poll Rates
Below a practical example for phasing the primary poll rate is provided to help you configure your
datablocks.
In situations where the mode of transmission is slow, such as radio or telephone communication, we
recommend phasing one or more datablocks to prevent overruns. Overruns can occur when the driver
attempts to process (read data from) more datablocks at one time than it can handle. By using phasing,
you can stagger when the driver processes a datablock.
Example
The following table shows an example of 10 datablocks processing every 10 seconds.
Name Primary Poll Rate Phase
Datablock0 10 0
Datablock1 10 1
Datablock2 10 2
Datablock3 10 3
Datablock4 10 4
Datablock5 10 5
Datablock6 10 6
67
GE9 OPC Server
Name Primary Poll Rate Phase
Datablock7 10 7
Datablock8 10 8
Datablock9 10 9
The driver processes the first datablock immediately after starting up. Each subsequent datablock
message is processed one second later instead of all at once.
NOTE: When transmission errors, retries, or other errors occur, the phasing you set may not remain
consistent. You may have to stop and restart the driver.
Creating Datablocks with the Power Tool
1. Start Database Builder and open the database EMPTY.PDB.

2. Start the Power Tool:
a. Select Programs from the Start menu.
b. Select FIX, Dynamics, or iFIX from the Programs menu.
c. Select GE9 Power Tool from the pop-up menu that appears.
3. When the Connection screen appears, select Local Server and click Connect.
4. Click the Setup button from the Run-time toolbar.

5. Click the Default Path tab.
6. Enter the default file name you want to use in the Default Configuration File Name field. If
you are using FIX, verify that the FIX Database path is in the Default Path for Configuration
File field. For example, if FIX is in C:\FIX32, then the Database path is C:\FIX32\PDB. If
you are using Dynamics, the default path is the iFIX Base path.
7. Close the Setup dialog box.
8. Click the Templates button from the Run-time toolbar and enter the defaults for your
channels, devices, and datablocks. The Power Tool uses these defaults when you add items to
your driver configuration.
9. Add the channels and devices you need. Make sure the devices you create match the names
referenced by your database blocks. For example, if you have a database block configured for
D11:1, create a device named D11.
10. Add datablocks to replace the poll records that were configured in the 6.x driver. If datablocks
are not configured, the database import will subsequently fail.
11. Stop the driver and import your original database to re-create the database blocks using
Database Builder.
12. Open the file \PDB\IMPORT.ERR with a text editor. This file contains any errors FIX
encountered while importing the database. Correct the errors listed in the file.
68
GE9 OPC Server
When configuring datablocks, you will use the following fields, buttons and check boxes:
• Access Time Field
• Address Length Field
• Block Name Field
• Connect Button
• Data Type Field
• Datablock Description Field
• Datablock Enable Check Box
• Deadband Field
• Default Configuration File Name Field
• Default Path for Configuration File Field
• Disable Outputs Check Box
• Enable Block Writes Check Box
• Ending Address Field
• Latch Data Check Box
• Phase Field
• Primary Rate Field
• Secondary Rate Field
• Starting Address Field
Access Time Field
Specifies how long the I/O driver scans a datablock by its primary poll rate when your process control
software no longer requests data from that datablock.
Whenever your process control software requests data from a datablock, the driver resets the access
time for that datablock. Once data requests stop for the datablock and the access time expires, the
driver scans the datablock by its secondary poll rate. If you set the secondary poll rate to DISABLED,
polling for that datablock stops until there is another request for data.
Make sure you specify an access time that is longer than the scan time entered for the associated
database block. Otherwise, your process control software receives old data.
Valid Entries
Example
To specify an access time of... Enter
1 second 1
69
GE9 OPC Server
To specify an access time of... Enter
1 minute 1:00
2 days 2:00:00:00
NOTE: You can force the I/O driver to always scan a datablock by its primary poll rate by entering
DISABLED in this field.
Address Length Field
Specifies the length of the datablock.

You can enter the address length manually or allow dynamic calculation from the values in the Starting
Address and Ending Address fields.
Example
Suppose you want to create a datablock with a starting address of R10 and an ending address of R125.
To do this, enter R10 in the Starting Address field and enter R125 in Ending Address field. The Power
Tool automatically completes the Address Length field with a value of R116.
For additional information about setting the address length, refer to Setting Datablock Address
Properties: Start, End, and Length
Block Name Field
Specifies the name of the selected datablock. This name is mainly for your reference. It is helpful to
use descriptive names you can recognize so that modifying or accessing information on the datablock
is easier.
NOTE: Each datablock name must be unique within the whole driver configuration.
Valid Entries
Up to 12 alphanumeric characters including underscores ( _ ) and hyphens ( - ).
Connect Button
Connects you to the I/O Server you have selected. The server can be local or remote.
Data Type Field
Specifies the datablock’s default data type. The driver uses this data type for the datablock if you do
not specify a database block hardware option. When a hardware option is specified, it overrides the
data type.
In general, you can mix data type and hardware option settings. For example, you can configure a
datablock as an unsigned integer and the database block that references it as a float. However, we
recommend that you configure exception-based database blocks with the same data type as the
70
GE9 OPC Server
datablock being referenced. Mixing data types with database blocks configured for exception-based
processing can yield unexpected results.
Valid Entries
Data Type Description
ASCII Text stored internal as a 16-bit integer. Provided for backward

compatibility.
Signed Integer Signed 16-bit integer.
Unsigned Integer Unsigned 16-bit integer.
Float 32-bit float point (IEEE)
Digital Discrete Bit.
Time Unsigned 32-bit integer. Provided for backward compatibility.
Long Unsigned 32-bit integer.
Signed Long Signed 32-bit integer.
Datablock Description Field
Contains text about the selected datablock. Entries in this field can be very helpful when you go back
to look at old configuration or report files, or when you need to modify an existing configuration that
you did not create. The more detailed and specific the information you enter in this field, the easier it
will be to identify the datablock at a later date.
Valid Entries
Datablock Enable Check Box
Enables the driver to poll the datablock when you select this check box. If you clear the check box, the
driver does not poll the datablock.
You may want to disable one or more datablocks in the following situations:
• You want to use the datablock for output only.
• You want to view data for a datablock intermittently.
• You want to isolate the datablock for debugging.
71
GE9 OPC Server
Deadband Field
Specifies the maximum acceptable data fluctuation in an exception-based FIX database block. Entering
a deadband value prevents the database block’s current value from changing when there is only a slight
fluctuation in data.
Valid Entries
Any positive number for analog datablocks. For digital datablocks, set the deadband to 0.
Example
Suppose the current value of a datablock is 50 and you set a deadband of 20, SAC updates the
exception-based database block when incoming values are less than or equal to 30 or greater than or
equal to 70.
To create an exception-based FIX database block:
1. Start FIX Database Builder.

2. Select Add Block from the Blocks menu.
3. Select the type of block you want to create.
4. Enter E in the Scan Time field.
Default Configuration File Name Field
Specifies the default I/O driver configuration file. The server loads this file on start-up.
Default Path for Configuration File Field
Specifies the default path for the driver’s configuration file. If the server does not find the default
configuration file in this path, it creates a new, empty configuration file.
Disable Outputs Check Box
Prevents output from the driver to the selected datablock when you select this check box.
You may want to disable outputs:
• To prevent control outputs that may be hazardous to someone performing maintenance or
repair on the process control hardware.
• To prevent erroneous writes to the datablock.
• To isolate a datablock for debugging.
Enable Block Writes Check Box
Sends all outstanding analog values for the current datablock to the process hardware.
72
GE9 OPC Server
Ending Address Field
Specifies the location in the device where the selected datablock ends.
You can enter the ending address manually or allow dynamic calculation from the values in the
Starting Address and Address Length fields.
Example
Suppose you want to create a datablock with a starting address of R1 and a length of 125. To do this,
enter R1 in the Starting Address field and enter 125 in the Address Length field. The Power Tool
automatically completes the Ending Address field with a value of R125.
For additional information about setting the ending address, refer to Setting Datablock Address
Properties: Start, End, and Length
Latch Data Check Box
Controls what an operator sees in a link when a communication error occurs.
When you... The operator sees...
Select the check box The last good value in the link.
Clear the check box A series of question marks (?????)
In FIX applications, the link’s current alarm status always displays COMM to indicate a
communication problem.
NOTES:
• FIX 6.15 does not support latched data. However, you can add support for latched data by
downloading the SAC Software Improvement Module (SIM) from the GE Fanuc’s web site.
• Analog Register and Digital Register blocks do not support latched data. Consequently, we
do not recommend using these blocks with the Latch Data option.
Phase Field
Sets the length of delay before the driver first attempts to read data for the datablock. When the phase
time expires, the driver resumes reading the datablock at the specified primary or secondary poll rate.
Valid Entries
Example
To specify a phase time of... Enter
1 second 1
73
GE9 OPC Server
To specify a phase time of... Enter
1 minute 1:00
2 days 2:00:00:00
Primary Rate Field
The rate at which the I/O driver polls the datablock for data.
Valid Entries
Example
To specify a primary poll rate of... Enter
1 second 1
1 minute 1:00
2 days 2:00:00:00
NOTE: Do not confuse the poll rate with the scan time that you enter for individual database blocks.
The poll rate defines how often the driver initiates requests for data from the process hardware. The
scan time defines how often SAC retrieves data from the driver’s common memory on a point-by-point
basis.
Secondary Rate Field
Specifies the rate at which the driver polls a datablock after the access time expires. The driver
maintains this poll rate on the datablock until there is another request for data.
The secondary poll rate runs in conjunction with the primary poll rate. Enter a secondary poll rate that
is longer than the primary poll rate to help minimize the CPU time while ensuring that the datablock is
always polled.
Valid Entries
74
GE9 OPC Server
Example
To specify a secondary poll rate of... Enter
1 second 1
1 minute 1:00
2 days 2:00:00:00
NOTE: Do not confuse the poll rate with the scan time that you enter for individual database blocks.
The poll rate defines how often the driver initiates requests for data from the process hardware. The
scan time defines how often SAC retrieves data from the driver’s common memory on a point-by-point
basis.
Starting Address Field
Specifies the location in the device where the selected datablock begins.
Valid Entries
Depends on your process hardware. Refer to Setting Datablock Address Properties: Start, End, and
Length for specific values.
Setting Default Values for Channels, Devices, and Datablock Properties

You can enter defaults for driver, channel, device, and datablock properties by clicking the Templates
button, , in the Run-time toolbar and displaying the Templates dialog box.
75
GE9 OPC Server
The driver uses the defaults you enter when you:

• Add addresses to the driver configuration from FIX Database Builder or an OLE application,
or
• Configure the driver from the Power Tool.
The Power Tool stores the default driver, channel, device, and datablock properties in the registry of
the computer on which you installed the GE9 I/O Server. For example, if you run the Power Tool and
connect to a server on another computer, the default values you enter are written to the remote server.
Setting default values can significantly decrease I/O driver configuration time. For example, if you
have 100 devices that have the same property settings except for the device name and IP address, you
can use the default settings for each device and modify only the two unique fields.
Example
Entering the following as channel default values:

Channel Description: Channel1
Channel Name: Channel1
76
GE9 OPC Server
Sets the registry on the server as shown below:
Creating Datablocks Inside FIX Applications

You do not have to use the GE9 I/O Driver Power Tool to create all of the driver datablocks. If you
have the right information, you can add datablocks while configuring your database in FIX Database
Builder.
To configure the driver from FIX Database Builder, you must know the following information about
the driver:
• The three-letter acronym for the driver. For the GE9 driver, the acronym is GE9.
• The data type of the data you want to receive.
• The name of the field device or process hardware that you want to collect data from, as
defined in the driver configuration.
• The register in the device that you want to collect data from.
• The type of signal conditioning you want to apply to the data.
• The specific digital point in the register you want to access. This information is only
necessary for digital database blocks. The GE9 driver accepts bit entries of 0 to 15.
Datablocks are automatically created for devices that already exist in the Power Tool. Devices are not
automatically created. Remember that the Device field in FIX Database Builder accepts the three-letter
driver acronym. The I/O Address field uses the device name assigned in the Power Tool followed by
the memory location in the device.
Refer to Entering Driver Information in FIX Database Builder for details on entering driver data in
Database Builder for automatic datablock creation.
IMPORTANT: Always stop any 7.x driver you have running before you import a database, reload a
database, or create multiple database blocks with the Generate command. If you leave the driver
running while you complete any of these tasks, the database may not load or import properly, or you
may have to restart FIX or Database Builder.
77
GE9 OPC Server
Creating Datablocks When Configuring a 7.x Driver

If you are upgrading from a version 6.x driver, you cannot use your old existing driver configuration or
any driver CSV files. However, with the Auto Create option in the 7.x driver, you can automatically
create all the datablocks you need from Database Builder.
To automatically create datablocks:
1. Start Database Builder and open the database EMPTY.PDB.

2. Start the Power Tool:
c. Select GE9 Power Tool from the pop-up menu that appears.
3. When the Connection screen appears, select Local Server and click Connect.
4. Click the Setup button from the Run-time toolbar.

5. Click the Default Path tab.
6. Enter the default file name you want to use in the Default Configuration File Name field. If
you are using FIX, verify that the FIX Database path is in the Default Path for Configuration
File field. For example, if FIX is in C:\FIX32, then the Database path is C:\FIX32\PDB. If
you are using Dynamics, the default path is the iFIX Base path.
7. Click the Advanced tab and select Auto Create On from the Server area.
8. Close the Setup dialog box.
9. Click the Templates button from the Run-time toolbar and enter the defaults for your
channels, devices, and datablocks. The Power Tool uses these defaults when you add items to
your driver configuration.
10. Add the channels and devices you need but do not create any datablocks. Make sure the
devices you create match the names referenced by your database blocks. For example, if you
have a database block configured for D11:1, create a device named D11.
11. Stop the driver and import your original database to re-create the database blocks using
Database Builder. As Database Builder creates each database block, it will also create
datablocks specified in I/O Address field.
12. With the Power Tool, adjust the datablock properties for each datablock created.
13. Open the file \PDB\IMPORT.ERR with a text editor. This file contains any errors FIX
encountered while importing the database. Correct the errors listed in the file.
Entering Driver Information in FIX Database Builder
To enter driver specifications for a database block in FIX Database Builder:
1. Select Add from the Blocks menu in the FIX Database Builder to add a database block.
Database Builder prompts you to select the type of database block.
2. Select the type of block and click OK. The block's dialog box appears as shown below.
78
GE9 OPC Server
Database Block Dialog Box
3. Enter a name in the Tag Name field.

4. Complete the driver fields with the appropriate information for your driver.
I/O Driver Fields
Refer to the following topics for valid entries for each field:
• Specifying I/O Drivers in the Device Field
• Specifying Hardware Options
• Specifying I/O Addresses
• Specifying Signal Conditioning
Specifying the I/O Driver in FIX Database Builder

The Device field in Database Builder identifies the I/O driver that the database block accesses. This
field accepts your driver’s the three-letter acronym. The default for this field is the first driver listed in
the Configured I/O Driver list box in the SCADA Configuration dialog box of the System
Configuration Utility (SCU). For the GE9 driver, enter GE9 in this field.
79
GE9 OPC Server
Specifying I/O Addresses in FIX Database Builder

You can specify the datablock address that the database block accesses in the Database Builder I/O
Address field. GE9 I/O Addresses typically consist of the device name and the datablock element. The
I/O address is specific to the driver. This field is not case sensitive.
The I/O Address for the driver has the following format:
DEVICE_NAME:ADDRESS[:BIT]
Where:
Parameter Description
DEVICE_NAME Is the name of the field device or process hardware that you want
to collect data from. This name must match the device name in the
driver configuration file.
ADDRESS Is a memory register in the device.
BIT Is a specific digital point in the register. This entry is only

necessary for digital database blocks. The driver accepts bit
entries of 0 to 15.
If you enter an I/O Address that is not defined by a datablock, the driver performs one of the following
operations if you enabled the Auto Create option:
• Adds the datablock to the specified device, or
• Extends an existing datablock to include the new address.
If you have not enabled the Auto Create option:
• Database Builder prompts you to start the Power Tool so that you can add the nonexistent
datablock to your driver configuration. You can then continue configuring the database block.
80
GE9 OPC Server
NOTE: You are also prompted to start the Power Tool whenever you enter the name of an undefined
device.
The driver optimizes the building of datablocks by automatically determining whether to extend an
existing datablock or add a new one. If you want to modify the datablock default values, open the GE9
I/O Driver Power Tool and make the changes to the configuration file.
You can enter the following special addresses into the I/O Address field of a Digital Output or Analog
Output block to perform certain events:
!SWITCH:NAME
!MODE:NAME
!POLL:NAME
!SEND:DATABLOCK
Where NAME is the name of the channel, device, or datablock you want to perform the event on.
Special Address Events
!SWITCH Toggles switching between the current and backup channel or

device when any value is written to a Digital Output or Analog
Output block.
!MODE Enables polling to the channel, device, or datablock specified

when a value of 1 is written to a Digital Output block (Analog
Output blocks are not supported). Disabling a specified object
occurs when a value of 0 is written to a Digital Output block.
!POLL Triggers a demand (one-shot) poll of:

• A channel and all of its devices and datablocks,
• A device and all its datablocks, or
• A specified datablock
when any value is written to a Digital Output or Analog Output
block.
81
GE9 OPC Server
!SEND Sends special command to the specified datablock when any value
is written to a Digital Output block. The command is sent only if
the Block Writes option is enabled in the datablock. The
command instructs the driver to send all outstanding analog values
in a single protocol message to the process hardware. When the
driver sends its outstanding writes, it also sends any unmodified
values in the datablocks that are changing using the last known
value. Consequently, we recommend relatively short poll times for
datablocks you are writing to so that the driver will have the most
up-to-date data.
You cannot use an Analog Output block to trigger block writes.
Specifying Signal Conditioning in Database Builder

With the Database Builder Signal Conditioning field, you can specify the method for converting raw
data to a value that FIX applications can use. Once you select a signal conditioning, the driver scales
(converts) the data to a value within the specified range.
Unsigned data types support many types of signal conditioning; signed values only support LIN signal
conditioning.
The type of signal conditioning you select must match the range of incoming values from the process
hardware. By matching the range of values in the process hardware, you ensure the driver can properly
convert the raw data values to the database block’s EGU range. For example, if the incoming values
are between 0 and 255, you would select 8BN signal conditioning.
GE9 Supported Signal Conditioning Types
• NONE
• 12BN Signal Conditioning
• 12AL Signal Conditioning (with alarming)
• LIN Signal Conditioning
• 3BCD Signal Conditioning
82
GE9 OPC Server

• 32KA Signal Conditioning (with alarming)
• 32KB Signal Conditioning
IMPORTANT: Most signal conditioning types with alarming return values with all 16 bits and
generate an OVER or UNDER range alarm if a value is outside the EGU range of the database block.
For example, if a database block using 8AL signal conditioning receives a value of 300, an OVER
range alarm is generated and the value 300 is displayed.
When 3BCD or 4BCD signal conditioning is used, out of range values are not displayed. For example,
if a database block using 3BCD signal conditioning receives a value of 1000, an OVER range alarm is
generated and question marks are displayed instead of the out of range value.
Signal Conditioning Parameters
Parameters for signal conditioning are described in the following topics:

• NONE Signal Conditioning
• LIN Signal Conditioning
• 12AL Signal Conditioning
• 32KA Signal Conditioning
• 32KB Signal Conditioning
NONE Signal Conditioning
Parameters for No Signal Conditioning
Description No signal conditioning
83
GE9 OPC Server
Input Range No scaling
Scaling Ignores EGU range in database block.
LIN Signal Conditioning
Parameters for LIN Signal Conditioning
Description 16-bit binary number.
Input Range 0 – 65535 or –32768 - +32767; the driver automatically determines

which input range to use.
Scaling Scales 16-bit binary values to the database block’s EGU range.
Read Algorithm Reads from a 16-bit register using the following algorithm:
Result = ((Raw_value/65535) * Span_egu) + Lo_egu
Read Algorithm Lo_egu – the database block’s low engineering value.

Variables
Span_egu – the span of the engineering values.
Raw_value – the value stored in the field device’s register.
Result – the scaled value stored in the database block.
Write Algorithm Writes to a 16-bit register using the following algorithm:

Result = (((InputData – Lo_egu)/Span_egu) * 65535) + .5
Write Algorithm Lo_egu – the low engineering value.

Variables
InputData – the database block’s current value.
Result – the value sent to the process hardware.
84
GE9 OPC Server
12AL Signal Conditioning
Parameters for 12AL Signal Conditioning
Input Range 0 – 4095; values outside this range generate an alarm.
Read Algorithm Reads from a 16-bit register using the same algorithm as 12BN, and
returns a status indicating whether the value is out of range and in an
alarm state, or OK.

Variables
Write Algorithm Writes to a 16-bit register using the same algorithm as 12BN, and returns
a status indicating whether the value is out of range and in an alarm state,
or OK.

Variables
12BN Signal Conditioning
Parameters for 12BN Signal Conditioning
85
GE9 OPC Server
Input Range 0 – 4095
Scaling Scales 12-bit binary values to the database block’s EGU range. Ignores
the most significant nibble (4-bits).

Variables


Variables
86
GE9 OPC Server
alarm state, or OK.

Variables
Write Algorithm Writes to a 16-bit register using the same algorithm as 13BN, and returns
a status indicating whether the value is out of range and in an alarm state,
or OK.

Variables
the most significant 3 bits.
87
GE9 OPC Server

Variables


Variables
alarm state, or OK.

Variables
88
GE9 OPC Server
Write Algorithm Writes to a 16-bit register with alarming using the same algorithm as
15BN, and returns a status indicating whether the value is out of range
and in an alarm state, or OK.

Variables
the most significant bit.

Variables

89
GE9 OPC Server

Variables
32KA Signal Conditioning
Parameters for 32KA Signal Conditioning
Description 16-bit signed value.
Scaling Scales incoming value (0-32000) to the EGU range in the database block.
Read Algorithm Reads from a 16-bit signed register using the following algorithm and
returns a status indicating whether the value is out of range, and in an
alarm state, or OK.

Variables
Write Algorithm Writes to a 16-bit signed register using the following algorithm and
returns a status indicating whether the value is out of range, and in an
alarm state, or OK.

Variables
90
GE9 OPC Server
32KB Signal Conditioning
Parameters for 32KB Signal Conditioning
Description 16-bit signed value.
Scaling Scales incoming value (0-32000) to the EGU range in the database block.
Read Algorithm Reads from a 16-bit signed register using the following algorithm:
Values greater than 32000 are clamped at Lo_egu + Span_egu. Values
below 0 are clamped at Lo_egu.

Variables
Write Algorithm Writes to a 16-bit signed register using the following algorithm:

Variables
3BCD Signal Conditioning
Parameters for 3BCD Signal Conditioning
Description 3-digit Binary Coded Decimal value.
91
GE9 OPC Server
Scaling Scales 3-digit Binary Coded Decimal values to the EGU range in the
database block.
Read Algorithm Reads from a 3-digit BCD register. The Raw_value is then separated into
three nibbles (4 bits) prior to scaling the value. Each nibble is examined
for a value greater than 9 (A-F hex). If a hexadecimal value between A
and F is found, a range alarm is generated, indicating the value is not
within BCD range. Otherwise, the value is scaled with the following
algorithm:

Variables
Write Algorithm Writes to a 3-digit BCD register using the following algorithm:

Variables
4BCD Signal Conditioning
Parameters for 4BCD Signal Conditioning
Description 4-digit Binary Coded Decimal value.
Scaling Scales 4-digit Binary Coded Decimal values to the EGU range in the
database block.
92
GE9 OPC Server
Read Algorithm Reads from a 4-digit BCD register. The Raw_value is then separated into
four nibbles (4 bits) prior to scaling the value. Each nibble is examined
for a value greater than 9 (A-F hex). If a hexadecimal value between A
and F is found, a range alarm is generated, indicating the value is not
within BCD range. Otherwise, the value is scaled with the following
algorithm:

Variables
Write Algorithm Writes to a 4-digit BCD register using the following algorithm:

Variables
Scaling Scales 8-bit binary values to the EGU range in the database block.
alarm state, or OK.
93
GE9 OPC Server

Variables
Write Algorithm Writes to a 16-bit register using the same algorithm as 8BN, and returns a
status indicating whether the value is out of range and in an alarm state,
or OK.

Variables
Scaling Scales 8-bit binary values to the EGU range in the database block.
Ignores the most significant byte.

Variables
94
GE9 OPC Server


Variables
Specifying Hardware Options in FIX Database Builder

You can select a data type for the process data stored by FIX from the Hardware Options field in
Database Builder. The data type you select overrides the data type of the associated datablock. If you
do not select a data type, FIX uses the datablock’s data type. For example, if you configure a datablock
with a Long data type and then select Float as the hardware option in Database Builder, the data type
for the datablock is Float because FIX overrides the datablock setting. For this reason, make sure the
data type you select in Database Builder is correct for the information that you are requesting.
Refer to the following table for a list of valid data types.
Supported Data Types
Data Type Description
UINT Unsigned 16-bit integer
SINT Signed 16-bit integer
Float 32-bit floating point (IEEE)
Long Unsigned 32-bit integer
SLong Signed 32-bit integer
95
GE9 OPC Server
Opening the Power Tool from FIX Database Builder
To open the GE9 I/O Driver Power Tool from FIX Database Builder
• Select GE9 from the Drivers menu. Any devices or datablocks that you added appear in the
Tree Browser.
Setting Up for Creating Datablocks Automatically in FIX Database Builder

FIX Database Builder uses the default settings for datablocks when you add a new database block that
refers to an undefined address. Default values may already be set for your application. To find out
what the default values are, open the GE9 I/O Driver Power Tool and click the Templates button in the
Run-time toolbar. When the Templates dialog box appears, you can display the default channel,
device, and datablock values by selecting a tab. To change a value, refer to Setting Default Values for
Channels, Devices, and Datablock Properties.
Verifying New Datablocks Created in FIX Database Builder

When you create a datablock in FIX Database Builder, it automatically adds to the driver server.
To verify that the datablock was added to the run-time configuration:
1. Open the GE9 Power Tool and select an item in the Tree Browser.
2. Press the F5 key to refresh the Tree Browser.
3. Expand the device containing the datablock you added.
Example
If you enter the following in the FIX Database Builder driver-specific fields:
And the default settings for datablocks entered in Power Tool's Templates dialog box are:
96
GE9 OPC Server
The Power Tool Tree Browser displays:
Press the F5 key to refresh the Tree Browser, and the Tree Browser displays:
And the properties for the datablock are:
97
GE9 OPC Server
Use the following I/O driver-specific fields in FIX Database Builder to set up the driver:
• Device
• Hardware Options
• I/O Address
• Signal Conditioning
Saving Datablocks Created in FIX Database Builder to the Configuration

File
Creating a datablock with Database Builder only adds the datablock to the run-time configuration, not
the driver configuration file.
To save the datablock to the configuration file, you can:
• Save the configuration file in the Power Tool at any time while FIX is running by clicking the
Save button.
• Let the datablock automatically add to the configuration file when you shut down FIX by
clicking an item in the Tree Browser and pressing Alt + Shift + S. When the Server window
appears, select Save on FIX Exit from the Server menu.
Save File On Exit
Saves the changes to the driver configuration file when the I/O Server shuts down. The server uses the
updated configuration file as the default configuration the next time it starts.
If you manually save the configuration file, be sure to select the default path specified in the Power
Tool; otherwise, the server will not find or load your updated driver configuration.
If you do not select this option, and you do not manually save your changes, modifications to the driver
98
GE9 OPC Server
configuration are only in effect while the server is running. Once the server shuts down, all changes are
lost.
To view the server, click an item in the Tree Browser and press Alt + Shift + S.
Using I/O Driver Report Files

You can use I/O driver report files (.CSV files) to document, create, or upgrade I/O driver
configuration binary files. .CSV files are Comma Separated Value files that you can view and edit in a
text editor or Microsoft Excel.
Driver .CSV files have the following sections:
• Report header
• Channel header
• Channel data
• Device header
• Device data
• Datablock header
• Datablock data
Section Description
Report Header Informational. Contains the driver name and the date of the report.
Channel Header Contains a list of all the channel properties. The channel header must
start with an exclamation point (!).
Channel Data Contains the values of the channel properties for your driver
configuration. The number of data values must match the number of
channel properties listed in the channel header. If you do not specify a
value for a property, it uses the default value for that property.
Device Header Contains a list of all the device properties. The device header must
start with an at-sign (@).
Device Data Contains the values of the device properties for your driver
device properties listed in the device header. If you do not specify a
value for a property, it uses the default value for that property.
Datablock Header Contains a list of all the datablock properties. The datablock header
must start with a pound sign (#).
99
GE9 OPC Server
Section Description
Datablock Data Contains the values of the datablock properties for your driver
datablock properties listed in the datablock header. If you do not
specify a value for a property, it uses the default value for that
property.
Example .CSV file displayed in a text editor
Section Example
Report [ I/O Driver Configuration Report, Wednesday May 14 1998, 11:26 AM]
Header
Channel !Name,Description,Enabled
Header
Channel Channel0,"This,Is,The,Description",1
Data Channel14,"This,Is,The,Description 1",0
Device @Channel,Name,Description,Enabled,PrimaryIPAddress,PrimaryReplyTimeout,
PrimaryRetries,PrimaryDelay,BackupIPAddress,BackupReplyTimeout,BackupRetries,BackupDelay
Header
Device Channel0,Device2,"This,Is,The,Description 2",1,100.100.100.2,03,3,10,,01,3,10

Data Channel0,Device6,"This,Is,The,Description
3",0,100.100.100.6,01,3,10,100.101.100.6,01,3,10
Channel14,Device8,"This,Is,The,Description
4",0,100.100.114.8,01,3,10,100.101.114.8,01,3,10
Datablock #Device,Name,Description,StartAddress,Length,PrimaryPollTime,SecondaryPollTime,Phase,
AccessTime,DeadBand,Enabled,LatchData,OutputDisabled
Header
Datablock Device2,Block13,,0,1,00,01,00,01:00:00,1,1,0,0
Data Device2,Block14,,50,1,00,01,00,01:00:00,1,1,0,0
Device2,Block15,,100,1,00,01,00,01:00:00,1,1,0,0
Device2,Block16,,150,1,00,01,00,01:00:00,1,1,0,0
Device2,Block17,,200,1,00,01,00,01:00:00,1,1,0,0
Device2,Block18,,250,1,00,01,00,01:00:00,1,1,0,0
Device2,Block19,,300,1,00,01,00,01:00:00,1,1,0,0
Device2,Block20,,350,1,00,01,00,01:00:00,1,1,0,0
100
GE9 OPC Server
You can import a .CSV file from the Power Tool or the I/O Server. Regardless of the method you
select, any errors in the .CSV file appear in the I/O Server window when you import it. To view the
errors, click an item in the Tree Browser and press Alt + Shift +S.
Example of Errors Displayed in I/O Server
101
Running the I/O Driver
This section describes how to run the I/O driver. The following topics are discussed:
• Viewing Statistics
• Starting and Stopping the I/O Driver
• Checking Communication
Viewing Statistics
The I/O Driver Statistics display shows statistics for the I/O driver. This is the highest level of driver
statistics and provides information about the entire system. The number of transmits, receives,
timeouts, retries, errors, and overruns are displayed for all channels, devices, and datablocks in the
current configuration.
To display the driver’s statistics, select the I/O driver icon from the Tree Browser and then click the
Statistics button in the Run-time toolbar.
Viewing Channel Statistics

The Channel Statistics display shows statistics for the selected channel. The number of transmits,
receives, timeouts, retries, errors, and overruns displayed are for all devices and datablocks configured
for the channel. You can also see the number of messages waiting for a response, the number of
messages waiting to be parsed, and the number of requests pending for the channel.
To display a channel’s statistics, select the channel from the Tree Browser and click the Statistics
button in the Run-time toolbar.
Viewing Device Statistics

The Device Statistics display shows the statistics for the selected device. The number of transmits,
receives, timeouts, retries, errors, and overruns are displayed for all datablocks configured for the
device.
To display a device’s statistics, select the device from the Tree Browser and click the Statistics button
on the Run-time toolbar.
Viewing Datablock Statistics

The Datablock Statistics display shows the statistics for the selected datablock. The number of
transmits, receives, timeouts, retries, errors, and overruns are displayed. Other Available statistics
include the last time the driver successfully read data from and wrote data to the datablock, the OPC
quality of the datablock, and the number of pending datablock writes.
To display the statistics for a datablock, select the datablock from the Tree Browser and click the
Statistics button in the Run-time toolbar.
103
GE9 OPC Server
Starting and Stopping the I/O Driver

This section describes how to start or stop the I/O driver. The following topics are discussed:
• Starting the I/O Driver from the Power Tool
• Starting the I/O Driver from the FIX SCU
• Setting the I/O Driver for Automatic Startup in FIX
• Starting the I/O Driver Manually from Mission Control
• Stopping the I/O Driver
Starting the I/O Driver from the Power Tool
To start the I/O driver from the I/O Driver Power Tool:
1. Specify a default path and configuration file name for the driver:
c. Enter the configuration file’s default name and default path in the fields provided.
2. Configure your channels, devices, and datablocks. Click the Enable check box for each
channel, device, and datablock you want to start.
3. Click the Start button from the Run-time toolbar. The driver processes all enabled
channels, devices, and datablocks.
If you want to start the driver automatically, you should also turn on the Auto Start option:
1. Select the Setup button in the Power Tool’s Run-time toolbar.
2. Select the Advanced tab in the Setup dialog box.
3. Click the Auto Start On option button from the Server area.
Starting the I/O Driver from the FIX SCU

IMPORTANT: You must install the GE9 driver in your root FIX or Dynamics directory to start it from
the SCU. If you have not installed the driver in this directory, uninstall it and then re-install it in the
proper path.
To start the GE9 I/O driver from FIX SCU:
1. Start the System Configuration Utility (SCU):

c. Select System Configuration from the context menu.
2. Click the SCADA button from the SCU toolbox.

3. Click the ? button next to the I/O Driver Name field for a list of available drivers.
104
GE9 OPC Server
4. Select the GE9 I/O driver.

5. Click Add.
6. Click Configure.
7. Click the Start button from the Power Tool.
NOTES:
• You must have an GE9 configuration file in your root Dynamics directory with a name
nodename.GE9. This file is necessary for iFIX to load the driver and is created by the
installation program when you install the GE9 driver. You also need a configuration file
with a different name that defines your channels, devices, and datablocks.
• If you are using FIX, nodename.GE9 resides in your Database path (C:\FIX32\PDB, by
default). Do not delete this file. FIX uses this file to load the driver. Use nodename.GE9
to define your channels, devices, and datablocks.
Setting the I/O Driver for Automatic Startup in FIX

You can configure a driver to start automatically by adding the I/O Control program to the list of
programs that are defined in the System Configuration Utility (SCU) to start automatically. FIX or
Dynamics may have already added this program to the list if you had one or more drivers installed
when you installed FIX. However, if you do not have any drivers installed, or I/O Control is not listed,
add the program to the Configured Tasks list in the SCU.
IMPORTANT: You must install the GE9 driver in your root FIX or Dynamics directory to start it
automatically from the SCU. If you have not installed the driver in this directory, uninstall it and then
re-install it in the proper path.
To set the I/O driver for automatic startup:

2. Click the Tasks button from the SCU toolbox.

3. Enter the Base path and IOCNTRL.EXE in the Filename field.
4. Enter the following command lines as needed, separated by a space:
/A Starts all I/O drivers identified in the SCADA

configuration.
/Sxxx Starts one I/O driver where xxx is the three-letter I/O driver
acronym.
5. Select the Background option button and click Add.
105
GE9 OPC Server
If you are connecting datablocks to one or more database blocks and need to access data with SAC,
add the GE9 I/O driver to the SCADA Configuration dialog box, as follows:
2. Select the ? button next to the I/O Driver Name field.
3. Select the GE9 driver from the dialog box and click OK. The following text appears in the I/O
Driver Name field:
GE9 – GE Fanuc Ethernet Series 90 v7.15
4. Click Add to add the selected I/O driver to the Configured I/O Drivers list box.
NOTES:
• You must have an GE9 configuration file in your root Dynamics directory with a
name nodename.GE9. This file is necessary for iFIX to load the driver and is created
by the installation program when you install the GE9 driver. You also need a
configuration file with a different name that defines your channels, devices, and
datablocks.
• If you are using FIX, nodename.GE9 resides in your Database path (C:\FIX32\PDB,
by default). Do not delete this file. FIX uses this file to load the driver. Use
nodename.GE9 to define your channels, devices, and datablocks.
• If you subsequently change the name of your SCADA server after installing the GE9
driver, FIX cannot automatically start the driver because the name of the node does
not match the name of the configuration file. To correct this, rename the
configuration file to match the name of your SCADA server. For example, if you
change the name of the SCADA server from SCADA1 to SCADA9, rename the
configuration file from SCADA1.GE9 to SCADA9.GE9.
Starting the I/O Driver Manually from Mission Control
To start the I/O driver manually from Mission Control:
1. Start Mission Control:

c. Select Mission Control from the context menu.
2. Click the I/O Control tab. This tab displays a list of each driver installed on your system,
along with the driver’s status (ACTIVE or STOPPED).
3. Select the driver you want to start from the Drivers list box.
4. Click Start. Note that if the selected I/O driver is already started, the Start button becomes a
Stop button.
NOTES:
• You must have an GE9 configuration file in your root Dynamics directory with a
name nodename.GE9. This file is necessary for iFIX to load the driver and is created
by the installation program when you install the GE9 driver. You also need a
configuration file with a different name that defines your channels, devices, and
datablocks.
106
GE9 OPC Server
• If you are using FIX, nodename.GE9 resides in your Database path (C:\FIX32\PDB,
by default). Do not delete this file. FIX uses this file to load the driver. Use
nodename.GE9 to define your channels, devices, and datablocks.
Stopping the I/O Driver
To stop the I/O driver manually from Mission Control:
1. Start Mission Control:

c. Select Mission Control from the context menu.
2. Click the I/O Control tab. This tab displays a list of each driver installed on your computer,
along with the driver’s status (ACTIVE or STOPPED).
3. Select the driver you want to stop from the Drivers list box.
4. Click Stop.
To stop the I/O driver from the GE9 I/O Driver Power Tool:
• Click the Stop button from the Run-time toolbar.
To stop the driver from a FIX application:
1. Open the GE9 I/O Driver Power Tool. Refer to Opening the Power Tool from FIX Database
Builder to learn how.
2. Click the Stop button from the Run-time toolbar.
107
Checking Communication
Provided below is a step-by-step procedure for setting up a single Data link and enabling
communication between FIX software and the process hardware with the GE9 I/O driver.
To add the GE9 I/O driver to a SCADA configuration and launch the GE9 I/O Driver
Power Tool:


3. Click the question mark (?) next to the I/O Driver Name field. A list of drivers installed on the
local node appears.
4. Select the GE9 I/O driver and click Add. The GE9 I/O driver adds to the Configured I/O
Drivers list.
5. Save and exit the SCU.
6. Start or restart FIX.
7. Start the GE9 Power Tool:
b. Select FIX, Dynamics, or iFIX from the Programs submenu.
c. Select GE9 Power Tool from the context menu.
To configure a device with the GE9 I/O Driver Power Tool:
1. With the GE9 I/O Driver Power Tool open, click the Add Channel button from the
Configuration toolbar.
2. Select the Enable check box to enable communication on the channel.
3. Select the channel that you added from the Tree Browser, and select the Add Device button
from the Configuration toolbar.
4. Enter the appropriate information. Change the device’s name to TESTPOINT.
5. Select the Enable check box.
To add a link that accesses the configured device in FIX Draw:
1. From the GE9 Power Tool, click the Setup button in the Run-time toolbar.
2. Click the Advanced tab and select Auto Create On from the Server area.
3. Open FIX Draw.
109
GE9 OPC Server
4. If the Toolbox does not appear on your screen, select Toolbox from the Tools menu.
5. Click the Data Link button on the Toolbox. A stamp appears.

6. Position the stamp on the screen and click once.
7. Enter a tagname.
8. Select Allow Data Entry in the Data Entry area of the dialog box. When the Choose Data
Entry method dialog box appears, click OK.
9. Select Controllable in the Data Link dialog box.
10. Click OK. A message box appears stating that the tagname does not exist and prompting you
to add it.
11. Click Add.
12. Select Analog Input and click OK.
13. Enter GE9 in the Device field.
14. Enter TESTPOINT:R15 in the I/O Address field.
Where TESTPOINT is the device name you entered in the Power Tool, and R15 is the register
in the device that you want to access for the tag.
15. Select OK. Database Builder automatically adds a datablock for the address R15.
16. Select QuickView from the View menu.
17. Data from the hardware appears in the link. If it does not, refer to the Troubleshooting section.
110
Optimizing the Driver
Select from the following topics for tips on optimizing your process.
• Optimizing Message Lengths
• Eliminating Excess Datablocks
• Using Primary and Secondary Poll Rates with Access Time
• Decreasing unnecessary stress on your system
• Sending Multiple Messages to the PLC
Optimizing Message Lengths

Automatically creating datablocks from FIX Database Builder is an easy way to reference device
addresses without having to use both an I/O driver configuration program (Power Tool, VB Client
application, or other) and FIX software. When you use this feature, you may find it necessary to
modify the datablock address properties to optimize throughput.
Example
The following example assumes that the device has a limit of 120 registers per datablock, and the
driver configuration has not been loaded.
1. Create a FIX tag referencing address 120.
Once this tag is added, the driver configuration has a datablock (we will call it DataBlock1 in
this example) with a start address of 130, an end address of 130, and a length of 1.
When this tag is added, the driver configuration has another datablock (we will call it
DataBlock2 in this example) with a start address of 5, end address of 5, and a length of 1.
When this tag is added, DataBlock2 in the driver configuration starts at register 5, ends at
register 120, and has a length of 116.
This behavior may not have a major impact on small configurations; however, for large configurations,
it is more efficient to extend DataBlock1 to start at 120 and end at 130 and change DataBlock2 to start
at 5 and end at 5 because the first scenario generates the following messages:
• Message 1: 5, length 116
The second scenario, by comparison, generates these messages:
In both cases, the same three registers of data are polled. However, by requesting smaller groups of
contiguous data, as in the second scenario, the driver configuration uses less bandwidth.
111
GE9 OPC Server
You should periodically start the I/O Driver Power Tool, examine the driver configuration datablock
address properties, and modify them for optimization.
Eliminating Excess Datablocks

Use the following procedure to eliminate excess datablocks if you enabled the Auto Create option in
your I/O driver configuration and you created FIX database blocks that required new datablocks. This
procedure removes any incorrectly configured or unused datablocks.
Using the Auto Create option also adds datablocks with default values. If you have modified the poll
rate or access time of one or more datablocks, use the procedure at the end of this topic.
NOTE: You may not be able to delete datablocks from the driver configuration because another
computer may start accessing them.
To eliminate excess datablocks:
1. With FIX running, open Mission Control, click the SAC tab, and click Stop, to stop SAC.
2. Open the I/O Driver Power Tool and delete all the datablocks. Do not delete the channels and
devices.
3. Return to Mission Control and the SAC tab. Click Start. The driver automatically adds the
necessary datablocks with the default settings defined in the Power Tool.
This procedure guarantees that the I/O driver configuration in the Power Tool matches what you are
accessing in your FIX database.
If you made specific modifications to one or more datablocks, such as a different poll rate for each
datablock on a device, use the following procedure.
To eliminate excess datablocks for specialized configuration files:
1. Export the current driver configuration file by saving it as a .CSV file.

2. Perform the three steps above for removing excess datablocks.
3. Compare the export file to the new configuration. Note any differences.
4. Modify the export file as needed.
5. Import the modified export file and save it as a driver configuration file.
Decreasing unnecessary stress on your system

• Clean up datablocks that you are not using for your process control system when possible.
Refer to How do I clean up excess datablocks? to learn how.
Sending Multiple Messages to the PLC

You can improve performance of your process hardware by configuring the GE9 driver to send
multiple messages to each configured device. When you configure the driver to send multiple
messages, the PLC stores the message in a memory buffer.
Sending multiple messages to a PLC provides the best performance improvement when your process
112
GE9 OPC Server
hardware is slow or very busy because it is more efficient for the device to retrieve messages from its
memory buffer than to wait for messages to be received from the network.
You can enable this feature by changing the value in the Simultaneous Messages per Device field from
one to a value up to four. Note that unless you configure a device with at least four datablocks, the
driver cannot send four messages at once. For example, if you configure a device with two datablocks
and you set the value in the Simultaneous Messages per Device field to four, the driver will send only
up to two messages at once.
The poll time of the datablocks also affects performance. For example, if you configure four
datablocks with a poll rate of 1 second, then the driver sends four messages at once each second.
However, if you stagger the poll rates or if you phase the datablocks, then the driver will send from 0
to 4 messages depending on the poll rates.
Other factors that can affect performance include:
• The speed of the PLC CPU and Ethernet Communications Module
• The PLC scan rate
• The network load
• The number of datablocks configured for each device
• The size of datablocks (the larger the datablocks, the more time it can take to process)
Consequently, setting the Simultaneous Messages per Device field to four may not yield the best
performance. You must test various combinations of the factors listed above to determine the optimal
performance for your application. If you start receiving timeouts or the driver starts sending retries,
lower the value in the Simultaneous Messages per Device field.
NOTE: Whenever you change the value in the Simultaneous Messages per Device field, stop and
restart the driver in order for your changes to take effect.
113
Troubleshooting Your System
The following topics are discussed in this section:
• How Do I?
• Troubleshooting
• The Most Common I/O Driver Problems
• Error Codes
• Tools for Troubleshooting the GE9 I/O Driver
• Getting Technical Support
How Do I?
• Choose poll rates?
• Eliminating Excess Datablocks
• Set up for remote configuration and control?
• Prevent the driver from writing to the hardware?
• Create reports of my driver configuration files?
• Save datablocks created in FIX Database Builder to the I/O driver configuration file?
• Open the GE9 I/O Driver Power Tool in FIX Database Builder?
• Configure my driver for demand polling?
• Poll a device only when data is being accessed?
• What is the difference between access time and scan time?
• Set up security for using the I/O Server remotely?
• Set up security when the driver runs as a service
• Force a switch between primary and backup channels or devices using FIX?
• Enable or disable channels, devices or datablocks using FIX?
• Write data to a datablock?
• View my driver statistics using tools for Troubleshooting the GE9 I/O Driver?
• Run the driver in simulation mode?
• Send multiple messages?
How do I choose poll rates?

Make the datablock’s poll rate shorter than your scan time. For example, if you have a database block
with a 5-second scan time, set the poll rate of the datablock it accesses to 2 or 3 seconds.
115
GE9 OPC Server
Keep in mind that if you set datablock poll rates to values that are shorter than needed, you impose
unnecessary stress on your system.
Zero Poll Rate
You can set the poll rate to zero; this setting forces the driver to run at its maximum rate and disables
overruns. In general, you should set the poll rate equal to 0 if it is more important to run the driver at
its maximum speed than to detect overruns.
How do I set up for remote configuration and control?

The GE9 I/O Server configures all the necessary remote settings when it is installed. However, before
you can use the server, your network administrator must set up security for using the server remotely.
Refer to How do I Set up Security for using the I/O Server Remotely for more information.
Once security is configured, you can select a remote server using the I/O Driver Power Tool. Refer to
Setting Up the GE9 I/O Server Connection to learn more.
If you cannot connect remotely, refer to the topic, I cannot connect to a remote server.
How do I prevent the driver from writing to the hardware?

You can use one of the following methods to stop output to the hardware:
Use the Disable Outputs option:
1. From the I/O Driver Power Tool Tree Browser, select the datablock that you want to disable.
2. Click the Configuration button from the Run-time toolbar.
3. Select the Disable Outputs check box for the datablock.
Use the Enable option:
1. In the I/O Driver Power Tool Tree Browser, select the channel, device, or datablock you want
to disable.
2. Click the Configuration button from the Run-time toolbar.
3. Clear the Enable check box for the channel, device, or datablock.
-Or-
• In FIX, create a link to a Digital Output block whose I/O address is !MODE:NAME, where
NAME is the channel, device, or datablock name you want to disable. Write a value of 0 to
disable the channel, device, or datablock.
This approach stops communication for the selected channel, device, or datablock.
Stop the I/O driver:
• Click the Stop button in the Power Tool’s Run-time toolbar.

-Or-
• In FIX Mission Control, highlight your driver and click Stop.
This approach stops all driver communication.
116
GE9 OPC Server
Use Simulation Mode:
1. Click the Setup button in the Power Tool’s Run-time toolbar.

2. Click the Advanced tab.
3. Click the Simulation Mode On option from the Nio area.
4. Restart the server.
This approach stops all writes to the process hardware.
How do I create reports of my driver configuration files?

You can create reports from your driver configuration files by saving them as Comma Separated Value
(.CSV) files. Once you create .CSV files, you can edit them in any third-party application that supports
.CSV files, such as Microsoft® Excel™ or a text editor. You can also create .CSV files in a third-party
application and open them with the I/O Driver Power Tool.
Refer to Using I/O Driver Report Files for details on creating reports.
How do I save datablocks created in FIX Database Builder to the I/O driver
configuration file?
You can use one of the following methods to save datablocks that you create in FIX:
• Click an item in the Tree Browser and press Alt + Shift + S. When the I/O Server window
appears, select SaveOnFIXExit from the Server menu. This selection enables the server to
save the driver configuration automatically when you exit FIX.
• Open the Power Tool and select Save from the File menu.
• Click an item in the Tree Browser and press Alt + Shift + S. When the I/O Server window
appears, select Save from the File menu.
How do I open the GE9 I/O Driver Power Tool in FIX Database Builder?
To open the GE9 I/O Driver Power Tool from FIX Database Builder:
1. Select GE9 from the Drivers menu in Database Builder. When the GE9 I/O Driver Power
Tool opens, any devices or datablocks that you added appear in the Tree Browser.
2. Modify and add channels, devices, and datablocks as needed.
How do I configure my driver for demand polling?

By entering a special I/O address in a Digital Output or Analog Output block, you can poll:
• Individual datablocks.
• Devices and all their datablocks.
• Channels and all their devices and datablocks.
This one-shot poll is called a demand poll.
You may want to set your driver up for demand polling if:
• The driver’s poll time is slow and you want to get data without having to wait for the next
117
GE9 OPC Server
update.
• You want to poll a device after opening a FIX operator display.
• You want to poll a device just before generating a report.
The poll occurs when you write a value to the block.
The I/O address syntax is: !POLL: NAME
Where NAME is the name of the datablock, device, or channel you want to demand poll.
How do I poll a device only when data is being accessed?
To poll the device only when data is being accessed:
1. From the I/O Driver Power Tool Tree Browser, select the datablock that you want to modify.
2. Enter DISABLED in the Secondary Rate field.
3. Enter a value in the Access Time field. Do not enter DISABLED in the field.
4. In the Primary Rate field, enter a value that is close to the time that the data in the device is
being updated.
What is the difference between access time and scan time?

Although the scan time is not a property of any driver object, it is important to know how it affects
driver throughput and data integrity. Whether using FIX View, or a Visual Basic Client, the rate at
which the data is being read or written is usually referred to as the scan time.
Example
Assume a Visual Basic Client has a timer function that calls the I/O Server’s ReadData method. The
ReadData interval is a property you can configure in a Visual Basic Timer. If the interval is set to 30
seconds, the Visual Basic Client calls the ReadData method every 30 seconds and accesses data every
30 seconds.
The data returned from the ReadData method is directly from the I/O driver memory. The data in
memory updates only when the driver polls. The ReadData method does not poll for data and waits for
a memory update before returning a value. Therefore, having a scan time longer than the access time
always returns old data and the driver flags the data quality as NO_DATA.
To resolve this problem, select a scan time that is shorter than the access time and enter an access time
that is longer than the primary or secondary poll time. For example, if you select a scan time of 30
seconds, you could use an access time of 45 seconds and a primary poll rate of 15 seconds.
If the secondary poll time is used, you may want to lengthen the scan time and access time to ensure
the driver has updated the datablock. For example, you could set the secondary poll time to 30 seconds,
the scan time to 45 seconds, and the access time to 60 seconds.
NOTES:
• Specifying an access time that is shorter than the primary poll time forces the driver to poll at
the access time interval; however, the data received is always old and is marked with the
NO_DATA quality flag.
• Similarly, entering a scan time that is longer than the access time also results in old data. The
data scanned each interval is as old as the access time minus the scan time and is marked
118
GE9 OPC Server
with the NO_DATA quality flag.
How do I set up security for using the I/O Server remotely?

The I/O Server supports DCOM (Distributed Component Object Model). If you want to grant only
certain users permission to launch or access the GE9 I/O Server, you can use the Windows utility,
DCOMCNFG.EXE, for configuring DCOM applications. DCOMCNFG.EXE is usually located in
your Windows \system32 directory.
IMPORTANT: We recommend that you allow client applications such as the FIX or the I/O Driver
Power Tool to automatically start the I/O Server rather than opening the Server independently from
the Windows environment. This is the intended method for Server start-up.
The I/O Server re-registers every time you double-click the I/O Server icon or use a shortcut to open it
from Windows or any Windows application such as Explorer. By re-registering, you reset the server’s
registry settings. When the I/O Server starts automatically from a client application, the registry
settings do not change.
If you start the I/O Server independently by selecting its icon or shortcut while the server is already
running, you overwrite the current custom security settings.
Example
The following procedures describe how to configure your system for the following conditions:
• Only the user that is logged on to the computer where the I/O Server resides can launch the
Server.
• Only administrators of the I/O Server host computer can access the server.
Use these procedures as a guide to implement security for your needs under Windows NT or Windows
2000:
To allow only Administrators access to the I/O Server:
1. Start DCOMCNFG.EXE and select the driver application from the list in the Applications tab.
The GE9 application name is GE9Drv I/O Driver Server.
2. Click Properties.
3. Click the Security tab to display the three modes of DCOM security.
4. Select the Use Custom Access Permissions option, and click the Edit button for access
permissions.
5. If Administrators and SYSTEM appears in the list on the Registry Value Permissions dialog
box, skip to step 9.
If Administrators or SYSTEM is not in the list, click Add.
6. Select the local computer name in the List Names From field.
7. Double-click Administrators and SYSTEM in the Names list to add it to the Add Names list
at the bottom of the dialog box.
8. Click OK to accept the selection and close the dialog box.
9. Select Administrators from the Name list and Allow Access from the Type of Access field.
Repeat this step for SYSTEM as well. For the other entries in the Name list, select Deny
Access from the Type of Access field.
119
GE9 OPC Server
To allow only the local user to launch the I/O Server:
1. Follow steps 1 through 3 above.

2. Select the Use Custom Launch Permissions option and click the Edit button for launch
permissions.
3. If INTERACTIVE and SYSTEM appears in the list on the Registry Value Permissions dialog
box, skip to step 7.
If INTERACTIVE or SYSTEM is not in the list, click Add.
5. Double-click INTERACTIVE and SYSTEM in the Names list to add it to the Add Names list
at the bottom of the dialog box.
6. Click OK to accept the selection and close the dialog box.
7. Select INTERACTIVE from the Name list and Allow Access from the Type of Access field
to allow launch access to the local user only. Repeat this step for SYSTEM as well. For the
other entries in the Name list, select Deny Launch from the Type of Access field to deny
launch access on the network.
After completing these steps, only users who have Administrator rights to the driver server host
computer can access the server. You can assign administrator rights with the Windows User Manager.
Use these procedures as a guide to implement security for your needs under Windows XP or Windows
Server 2003.
To allow only Administrators access to the I/O Server:
1. Using the Start Menu, launch DCOMCNFG.EXE. The Component Services dialog box
appears.
a. Select Run from the Start Menu.
b. Type DCOMCNFG in the field provided and click OK.
2. Double-click the folder Component Services from the system tree.
3. Double-click the folder Computers from the system tree.
4. Double-click the folder My Computer from the system tree.
5. Double-click the folder DCOM Config from the system tree.
6. Locate the driver application in the system tree and right-click it. The GE9 application name
is GE9Drv I/O Driver Server.
7. From the context menu, select Properties. The driver’s Properties dialog box appears.
9. Select Customize from the Access Permissions area and click the Edit button for access
permissions. The Access Permissions dialog box appears.
10. If Administrators and SYSTEM appears in the list, skip to step 15.
If Administrators or SYSTEM is not in the list, click Add. The Select User, Computers, or
Groups dialog box appears.
11. Click Locations. You are prompted to log in.
12. Click Cancel. The Locations dialog box appears.
13. Select the local computer name in the Locations field and click OK to return to the Select
120
GE9 OPC Server
User, Computers, or Groups dialog box.

14. Enter Administrator in the Enter the Objects Name to Select field. Repeat this step for
SYSTEM, if necessary and click OK to return to Access Permissions dialog box.
15. Select Administrator from the list and select the Allow check box. Repeat this step for
SYSTEM as well. For the other entries in the list, select the Deny check box.
To allow only the local user to launch the I/O Server:
1. Follow steps 1 through 7 above.

2. Select Customize from the Launch Permissions area and click the Edit button for launch
permissions. The Launch Permissions dialog box appears.
3. If Administrators and SYSTEM appears in the list, skip to step 8.
If Administrators or SYSTEM is not in the list, click Add. The Select User, Computers, or
Groups dialog box appears.
7. Enter INTERACTIVE in the Enter the Objects Name to Select field. Repeat this step for
SYSTEM, if necessary and click OK to return to Launch Permissions dialog box.
8. Select INTERACTIVE from the list and select the Allow check box. Repeat this step for
SYSTEM as well. For the other entries in the list, select the Deny check box.
After completing these steps, only users who have Administrator rights to the driver server host
computer can access the server. You can assign administrator rights with the User Accounts applet in
Control Panel.
How do I set up security when the driver runs as a service?

To set up security for the GE9 driver, you must configure DCOM (Distributed Component Object
Model). Configuring DCOM can be difficult. To simplify the process, we recommend that you grant
access to everyone to get started. Later, when security is configuring correctly, you can reconfigure
DCOM and restrict access.
You can grant everyone of access to the GE9 server using the Windows utility, DCOMCNFG.EXE, for
configuring DCOM applications. DCOMCNFG.EXE is usually located in your Windows \system32
directory.
To configure DCOM when the GE9 driver runs as a service under Windows NT or
Windows 2000:
1. Start DCOMCNFG.EXE and double-click the GE9Drv I/O Server from the list in the
Applications tab.
3. Select the Use Custom Access Permissions option, and click the Edit button for access
permissions. The Registry Value Permissions dialog box appears.
4. Click Add. The Add Users and Groups dialog box appears.
121
GE9 OPC Server
6. Double-click Everyone (All Users) in the Names list to add it to the Add Names list at the
bottom of the dialog box.
7. Click OK to accept the selection and return the Registry Value Permission dialog box.
8. OK to accept the changes to the access permission properties.
9. Select the Use Custom Launch Permissions option and click the Edit button for launch
permissions. The Registry Value Permissions dialog box appears.
10. Repeat steps 4 through 9 for launch permission properties.
11. Click OK to accept your changes to GE9 server properties and return to the Applications tab.
12. Click OK to close the DCOMCNFG.EXE utility.
To configure DCOM when the GE9 driver runs as a service under Windows XP or
Windows Server 2003:
1. Using the Start Menu, launch DCOMCNFG.EXE. The Component Services dialog box
appears.
a. Select Run from the Start Menu.
b. Type DCOMCNFG in the field provided and click OK.
2. Double-click the folder Component Services from the system tree.
3. Double-click the folder Computers from the system tree.
4. Double-click the folder My Computer from the system tree.
5. Double-click the folder DCOM Config from the system tree.
6. Locate the driver application in the system tree and right-click it. The GE9 application name
is GE9Drv I/O Driver Server.
7. From the context menu, select Properties. The driver’s Properties dialog box appears.
9. Select Customize from the Access Permissions area and click the Edit button for access
permissions. The Access Permissions dialog box appears.
10. Click Add. The Select User, Computers, or Groups dialog box appears.
14. Enter Everyone (All Users) in the Enter the Objects Name to Select field and click OK to
return to Access Permissions dialog box.
15. 1Select Everyone from the list and select the Allow check box and click OK to return to the
Properties dialog box.
16. Select Customize from the Launch Permissions area and click the Edit button for launch
permissions. The Launch Permissions dialog box appears.
17. Repeat steps 10 through 15 for launch permission.
18. Click OK to accept your changes to GE9 server.
To learn more about configuring DCOM for specific users, refer to How do I set up security for using
the I/O Server remotely?.
122
GE9 OPC Server
How do I force a switch between primary and back-up channels or devices

using FIX?
You can force the current channel or current device to toggle between its primary or back-up settings
by entering a special I/O address into a Digital Output or Analog Output block. The driver switches
channels or devices when you write a value to the block.
I/O address syntax: !SWITCH:NAME
Where NAME is the name of the channel or device you want to switch.
How do I enable or disable channels, devices or datablocks using FIX?

You can enable or disable a channel, device, or datablock by entering a special I/O address into a
Digital Output block. Write a value of 1 to the block to enable it, or write a value of 0 to disable it.
I/O address syntax: !MODE:NAME
Where NAME is the name of the channel, device, or datablock you want to enable or disable.
How do I write data to a datablock?

You can write data to various registers in the hardware at one time using the Block Writes option. This
option provides a special "send" command that instructs the driver to send all outstanding writes in a
single protocol message.
To send block writes through FIX:
1. Create a datablock with a maximum length of 99 words (198 bytes).

2. Enable block writes in the datablock.
3. Create a Digital Output block with the following I/O address:
!Send:DataBlockName
Note that only datablock names are valid with the !Send control address. You cannot trigger block
writes using any of the following items:
• Channel and device names in place of a datablock name.
• Analog Output blocks in place of a Digital Output block.
123
GE9 OPC Server
How do I run the driver in simulation mode?
To run the I/O driver in simulation mode:
1. Start the Power Tool.

2. Select the Setup button in the Run-time toolbar.
3. Select the Advanced tab in the Setup dialog box.
4. Click the Simulation Mode On option button.
5. Restart the server.
To restart the server:
1. Shut down all server clients including the FIX. This action shuts down the server.
2. Restart the FIX.
Once the server restarts, you can create your operator displays and process databases with real I/O
addresses. Later, when you want to switch to real process hardware, turn off simulation mode and
restart the server again. You can do this without changing your configured I/O addresses.
How do I send multiple messages to a device?

NOTE: Many factors can affect performance. Refer to the topic Sending Multiple Message to a PLC
for more information.
Whenever you change the value in the Simultaneous Messages per Device field, stop and restart the
driver in order for your changes to take effect.
Troubleshooting
Select from the Troubleshooting tips below to find out how to correct problems with your I/O driver.
To enter new support issues, go to GE Fanuc’s WWW support site.
To search for an updated version of your driver, go to GE Fanuc’s WWW SIM site.
• Tools for Troubleshooting the GE9 I/O Driver

• The driver does not load
• The driver loads but does not start polling
124
GE9 OPC Server
• The driver does not communicate to any devices

• The driver is not transmitting messages
• The driver transmits messages but does not receive messages
• The driver communicates to some but not all of my devices
• The driver communicates to some but not all the datablocks for a device
• My driver is communicating but I am receiving question marks. When I look in alarm history,
the data quality is marked with NO_DATA flag.
• I cannot connect to a remote server
• I cannot see the driver in the FIX Database Builder
• I am receiving old data in my display
• What do the numbers in the Errors field of the Power Tool's statistic display mean?
• I am receiving overruns
• My message rate is slow
• My driver stops running after a period of time
• I do not receive driver messages in Alarm History
• Automatic driver startup does not work
• I cannot configure the driver to send multiple messages
• Nothing happens when I select Next Channel in Mission Control
The driver does not load
If you think the driver didn’t load:
• Start the Event Viewer in Windows. The Event Viewer displays specific messages regarding
loading and starting the driver. Problems loading the driver are logged to this file. To learn
more about using this application, refer to Using the Event Viewer.
If you have been loading the driver from a FIX application:
• Shut down the FIX application and try starting the driver without FIX running. This removes
problems associated with applications other than the I/O driver.
If you are starting a driver on a remote computer and it does not load:
• Try starting the driver on your local node. If it loads correctly on the local computer, you may
be experiencing network problems or security issues. You must configure DCOM
(Distributed Component Object Model) to provide access to a remote server. Refer to How do
I Set up Security for using the I/O Server Remotely for more information.
If the driver still does not load:
• Rename the default configuration file so the driver loads a blank configuration. If the
configuration file is corrupt, it may prevent the driver from loading. You can retrieve a
corrupted configuration file if you save it as a .CSV file; otherwise, you have to rebuild the
125
GE9 OPC Server
driver configuration.
The driver loads but does not start polling
If the driver loads but does not start:
1. Verify that the channels, devices, and datablocks are enabled. You can examine these
properties in the GE9 I/O Driver Power Tool.
2. IF FIX is not your Human-Machine Interface (HMI) software, make sure the Auto Start
option is turned on:
a. Select the Setup button in the Power Tool’s Run-time toolbar.
b. Select the Advanced tab in the Setup dialog box.
c. Click the Auto Start On option button from the Server area.
If you are starting the driver from FIX:
1. Verify that IOCNTRL starts from the System Configuration Utility (SCU). You should have a
/a on the command line for the IOCNTRL to start the driver automatically.
The driver does not communicate to any devices

Or I receive ????? in my operator display links.
If the driver loads and starts but you are not getting any information from your devices, examine the
statistics in the GE9 I/O Driver Power Tool for information about the driver’s current state. Start at the
highest level of the driver statistics:
1. Select the I/O driver icon from the GE9 I/O Driver Power Tool’s Tree Browser and click the
Statistics button in the Run-time toolbar. The I/O driver’s statistics display in the
Power Tool.
2. If you see errors, examine the channel statistics to find which channel(s) has the problem
device(s).
3. Examine the device(s) statistics as well. The device statistics may help to narrow your search.
If you have multiple devices and the driver is not communicating with any of them, you most likely
have one of the following problems:
• You have a problem with your cable.
• Verify that your computer’s TCP/IP protocol stack is correctly installed and configured.
• Verify that the PLC has been correctly configured for TCP/IP communications. Also obtain
the hardware’s IP address.
• Using the PLC’s IP address, try to ping it. If the ping is successful, it will confirm the
hardware has been correctly installed and that the cable is not the problem.
126
GE9 OPC Server
• Make sure that the IP address you are using in your driver configuration has been added to
your computer’s HOSTS file. After adding the IP address, restart the computer so that your
changes take effect.
The driver is not transmitting messages
If the driver is not transmitting messages:
1. Examine the green arrow in the GE9 I/O Driver Power Tool to ensure the driver starts; the
arrow should be selected. If it is, select the Stop button and then click the Start button again.
2. Select an item in the Tree Browser and press Alt + Shift + S to display the Server window.
Make sure the window contains a message that the driver has started.
3. Make sure the device can communicate over the network using a utility such as ping.
4. Monitor the server’s display window or start the FIX Alarm History application to ensure the
driver connects to the device.
5. Examine the cable to ensure it is plugged in.
6. If you are running the driver with FIX, make sure you have a configuration file with the name,
nodename.GE9, where nodename is the name of your FIX node, in the Database path
(C:\FIX32\PDB, by default). If you are using Dynamics, the file resides in the root Dynamics
directory. This file is needed for FIX and iFIX to load the driver; do not delete it.
The driver transmits messages but does not receive messages
To find out why your driver is transmitting but not receiving messages:
1. When communicating with an Ethernet device, attempt to ping the IP address and make sure
that you can reach the device from your computer.
2. Examine your process hardware. See if any diagnostic lights on the device indicate what the
problem is.
At this point, we strongly recommend reducing the configuration to one channel, one device,
and one datablock. This makes it easier to focus on the problem.
To reduce the configuration to one channel, one device, and one datablock:
1. Disable all but one channel.

2. On the enabled channel, disable all but one device.
3. On the enabled device, disable all but one datablock.
4. Verify that the device’s IP address is correct. Usually, the wrong IP address returns an error
message; however, some hardware devices do not reply at all if you enter the wrong IP
address.
The driver communicates to some but not all of my devices

Or I receive ?????? in some of my operator display links.
127
GE9 OPC Server
If you are receiving errors in the device statistics Errors field:
1. Verify that the device’s IP address is correct.

2. Try to ping the device.
To examine device statistics in the Errors field:
1. Select the device that is not communicating from the GE9 I/O Driver Power Tool’s Tree
Browser and click the Statistics button in the Run-time toolbar. The device’s statistics display
in the Power Tool Properties Viewer.
2. If there are error numbers in the Errors field, look up the error number in the table Error
Codes. These errors are returned from the hardware. If they are not listed in the table, consult
your hardware protocol manuals. They usually list the error number and a description of the
problem.
The driver communicates to some but not all the datablocks for a device
If you are receiving errors for datablocks in the statistics section of the GE9 I/O Driver
Power Tool:
1. Verify that each datablock address is valid and exists. The most common error for datablocks
is requesting memory locations that are not configured in the hardware.
2. Look up the error number in the table Error Codes. These errors are returned from the
hardware.
If the error number is not listed in the table, correct your hardware protocol manuals. They
usually list the error number and a description of the problem.
If you are not receiving errors in the statistics section:
• Refer to What is the Difference between Access Time and Scan Time to ensure the
datablock’s access time is set correctly.
I cannot connect to a remote server
If you cannot connect to a remote server:
• Make sure you have entered the correct name or IP address for the remote server. Also verify
that the security for using the server remotely has been set up. Refer to How do I Set up
Security for using the I/O Server Remotely for more information.
If you cannot see the remote server from Microsoft Explorer or by using the Ping
program:
• You have a networking problem. You may want to speak to your network administrator.
If you were running the Power Tool and you changed the server location:
1. Exit the Power Tool and restart it. If this is not the problem, proceed with the following steps.
2. Physically go to the server and verify that it started successfully.
128
GE9 OPC Server
3. If the server does not start, refer to My driver does not load.
4. If the server does start, leave the server running and try to connect to it from another
computer.
I cannot see the driver in the FIX Database Builder

FIX has not loaded the driver. Make sure you have installed the driver in the root FIX or Dynamics
directory. If the driver is installed in a different path, uninstall it and then re-install it in the root FIX or
Dynamics directory.
Next, configure FIX to load your driver:
1. Start the System Configuration Utility (SCU) and verify that the driver is listed in the
SCADA Configuration dialog box. If it is not listed, add it.
2. Verify that the SCU is configured to start the IOCNTRL program with a /a command line
parameter in the Task Configuration dialog box.
Refer to Setting the I/O Driver for Automatic Startup in FIX to learn how to complete both tasks.
I am receiving old data in my display

Data returned from a datablock read comes directly from I/O driver memory. The data in memory
updates when the driver polls. A read from SAC or View does not prompt the I/O driver to poll for
data. If you enter a scan time that is longer than the datablock’s access time, the I/O driver always
returns old data and the driver flags the data quality as NO_DATA.
To resolve this problem, select a scan time that is shorter than the access time and enter an access time
that is longer than the primary or secondary poll rate.
Example
To receive up-to-date data, you could set the poll rate, access time, and scan time as follows:
Poll rate: 1 second
Access time: 3 seconds
Scan time: 2 seconds
If this is not the problem, you may have the Latch Data option enabled while experiencing a
communication failure. To determine if this is the problem, turn off the Latch Data option. If the links
on the screen change to question marks, you are experiencing a communication failure. Refer to the
topic Troubleshooting to resolve this issue.
You also receive old data if your exception deadband is larger than the change in data. For example, if
your deadband is 20 but your data fluctuates between 5 and 15, the deadband is never exceeded and no
new data is sent. To correct this problem, reduce the deadband value.
I am receiving overruns
Overruns do not necessarily indicate an error condition. They merely indicate that the driver is trying
to process more data requests than the process hardware can handle. You can minimize the number of
overruns you receive by changing the driver configuration.
129
GE9 OPC Server
To reduce overruns:
1. Try increasing the poll times for the individual datablocks.

2. If the overruns are sporadic or only occur when the driver starts, try phasing the datablocks so
that the driver does not attempt to poll all the datablocks at the same time.
3. If your datablocks are phased, try stopping and restarting the driver since phasing only
happens when the driver starts.
My message rate is slow
If you have a slow message rate:
• Examine your devices for incorrect IP addresses. If the driver is sending messages to devices
that are offline or do not exist, the driver performs a series of timeouts and retries causing a
slow message rate. If you plan to have a device offline for a period of time, disable the device
until it is back online.
My driver stops running after a period of time

You may have a power-saving option enabled in your computer’s BIOS. Power-saving utilities may
put the hard drive in sleep mode and turn off the monitor to save power. If you do have a power-saving
utility, disable it.
Likewise, screen savers can stop your driver from running, depending on the screen saver. If you have
a screen saver enabled, disable it and turn off your monitor when no one is actively using your
SCADA server.
I do not receive driver messages in Alarm History

You may have started the I/O Server before starting FIX. Typically, the I/O Server starts when you
start a driver configuration program, such as I/O Driver Power Tool or a Visual Basic client
application.
To make sure you receive driver messages in Alarm History:
1. Shut down FIX and the I/O Driver Power Tool.

2. Start the System Configuration Utility (SCU) and click the Tasks button from the SCU
toolbox.
3. Enter the Base path and IOCNTRL.EXE in the Filename field.
4. Enter the /a command line parameter in the Command Line field.
5. Select the Background option button and click Add.
6. Save the SCU configuration and start FIX. The GE9 automatically starts and you should see a
message that the driver started.
Automatic driver startup does not work

To automatically start the driver, install it in your root FIX or Dynamics directory. If you have not
installed the driver in this directory, uninstall it and then re-install it in the proper path.
130
GE9 OPC Server
Next, start the Power Tool and verify that it is configured correctly:
1. Verify that the channels, devices, and datablocks are enabled.
2. Make sure the Auto Start option is turned on:
a. Select the Setup button in the Power Tool’s Run-time toolbar.
b. Select the Advanced tab in the Setup dialog box.
c. Click the Auto Start On option button from the Server area.
Lastly, start the System Configuration Utility (SCU) and verify it is configured correctly:
1. Click the SCADA button from the SCU toolbox. You should see the following text in the
dialog box that appears:
GE9 – GE Fanuc Ethernet Series 90 v7.x
2. If you do not see this text, Select the ? button next to the I/O Driver Name field.
3. Select the GE9 driver from the dialog box and click OK.
4. Click Add to add the selected I/O driver to the Configured I/O Drivers list box.
5. Click OK again to close the SCADA Configuration dialog box.
6. Click the Task Configuration button from the SCU toolbox. You should see IOCNTRL.EXE
/a listed in the dialog box that appear.
7. If you do not see this text, enter the Base path and IOCNTRL.EXE /a in the Filename field.
8. Click OK to save your changes and save your SCU configuration.
9. Restart FIX. The driver should automatically start.
I cannot configure the driver to send multiple messages

5. Enter the number messages you want to send to a device simultaneously.
NOTE: Many factors can affect performance. Refer to the topic Sending Multiple Message to a PLC
for more information.
Whenever you change the value in the Simultaneous Messages per Device field, stop and restart the
driver in order for your changes to take effect.
131
GE9 OPC Server
Nothing happens when I select Next Channel in Mission Control

Mission Control displays driver-level statistics for GE Fanuc I/O drivers, version 7.0 or greater. The
statistics displayed are not single-channel statistics, but a statistics summary of all channels.
To view statistics for a single channel, device, and datablock:
1. Open the I/O Driver Power Tool.

2. Select the channel, device, or datablock that you want to view statistics on.
3. Select Statistics from the View menu. The statistics display in the Properties Viewer.
The Most Common I/O Driver Problems

Some of the most common problems people encounter when setting up and using I/O drivers are
caused by one or more of the following:
• Using incorrect or faulty cable connections. To verify your connections, refer to the cable
diagram in your hardware documentation. Another test that usually verifies that the cable is
correct is to attempt to communicate to the hardware with the programming software through
the same cable.
• Specifying an incorrect IP address for the process hardware in your driver configuration.
Review your driver configuration and your process hardware.
• Failing to run SAC. You cannot access data from your I/O driver in View until SAC is
running.
• Setting the write protect switch on the hardware. If the I/O driver reads values but does not
write values, make sure the switch is not set. Also, start the Power Tool and verify that the
Disable Output option is not enabled for the datablock.
• Attempting to communicate to areas of memory not defined in the controller. Verify that each
datablock’s address is valid.
Error Codes
Error codes display in the Errors field of the Power Tool’s statistics display and in the Mission
Control’s DRVST fields.
132
GE9 OPC Server
DRVST Field Description
DRVSTA The number of overruns. An overrun occurs when the driver tries to
process more data than it can handle. A high number of overruns indicate
that your driver cannot poll all of the enabled datablocks at the rate
specified. It also indicates that the driver is poorly configured and, as a
result, your data is not updating at the specified poll rate.
NOTE: Setting the poll rate to zero forces the driver to run at its
maximum rate and disables overruns. Set the poll rate equal to 0 if it is
more important to run the driver at its maximum speed than to detect
overruns.
To reduce overruns:
1. Try increasing the poll times for the individual datablocks.
2. If the overruns are sporadic or only occur when the driver starts,
try phasing the datablocks so that the driver does not attempt to
poll all the datablocks at the same time.
3. If your datablocks are phased, try stopping and restarting the
driver since phasing only happens when the driver starts.
Tools for Troubleshooting the GE9 I/O Driver
The Statistics View in the GE9 I/O Driver Power Tool
The Power Tool displays communication statistics for each datablock, device, channel, and the entire
driver. Displaying these statistics is useful for narrowing down which part of the driver is not
functioning. To view the statistics, select a datablock, device, or channel from the Tree Browser and
click the Statistics button on the Run-time toolbar.
The Statistics in FIX Mission Control
Mission Control is the main FIX tool for monitoring background tasks, such as SAC, Historical
Collect, and I/O drivers. Using Mission Control, you can start and stop a driver, and view driver error
numbers. This is useful for quickly determining if the driver is having a problem.
Mission Control also provides a summary of driver-level statistics. To see the statistics for each
channel, use the GE9 Power Tool.
The Windows Event Viewer
The driver reports any major errors to the Windows Event Viewer. To learn more about using this
application, refer to Using the Event Viewer.
The Alarm History Window in FIX
Because the I/O driver reports event messages to the Alarm History application in FIX, you can use
this program for debugging your driver. The events reported include when the driver:
• Starts and stops.
133
GE9 OPC Server
• Connects and disconnects.

• Switches channels and devices.
• Fails to communicate and subsequently recovers.
Refer to the FIX documentation for details on enabling alarm services.
The Message Log in the I/O Server program
The message log in the I/O Server program tracks the following events:
• The date and time a configuration file loads.
• Which configuration file loads. If the driver is not loading the configuration file you want,
you can change the default file name and location in the Power Tool’s Setup dialog box.
• The date and time other applications attach to the server. This data can help you determine if
someone is attached and making changes to the server you are working on.
• CSV import errors.
To view the I/O Server program:
1. Open the Power Tool.

2. Select an item from the Tree Browser.
3. Press Alt + Shift + S.
The options in the program’s View menu let you choose the types of messages to display. The message
priority is as follows:
1 – Errors
2 – Warnings
3 – Information
The default setting for the Server is to display errors, warnings, and informational messages.
Once you select the messages you want to display, you must restart the Power Tool before your
changes can take effect.
To close the I/O Server Program:
1. Select an item from the Tree Browser.

2. Press Alt + Shift + S.
Using the Event Viewer

GE Fanuc’s Version 7.x drivers take advantage of a Windows feature known as the Event Viewer. This
feature allows software to write messages and data to the Windows Event Log. These messages can
then be viewed using the Event Viewer application. Version 7.x drivers use this ability primarily to log
information about problems that arise during execution, particularly in the lowest layers of the driver
where reporting the problem to users is more difficult. It also allows the messages logged to include
specific information about the error. For instance, if the memory object encounters a problem while
mapping an area of global memory with the "CreateFileMapping()" Win32 function, it not only reports
that the error happened, but it can also translate the error code returned by Windows and include that
text as well.
134
GE9 OPC Server
The Event Viewer contains three different categories of messages: System, Security, and Application.
This I/O driver writes its messages to the Application log.
To view messages that might be generated by the driver:
1. Start the Event Viewer:

2. Select the Application log from the Log menu. All the log messages associated with the
Application log appear. Any message specific to your driver contains the driver’s acronym
(GE9) in the Source column.
To view the message, use one of the following techniques:
• Select a message and press the Enter key.

• Highlight a message and select Detail from the View menu.
• Double-click the message.
Information that may be helpful for troubleshooting your I/O driver includes:
• Time – The time that the message was logged.
• Computer – The name of the computer that the message was logged on.
• Type – The severity of the message. Options include: Error, Information, and Warning.
• Description – The actual message logged.
• Data – The specific data associated with the message. The GE9 driver rarely uses this
information.
Getting Technical Support
Support for the GE9 I/O driver
By World Wide Web
To enter new support issues, go to GE Fanuc’s WWW support site.
To search for an updated version of your driver, go to GE Fanuc’s WWW SIM site.
By Phone
GE Fanuc Technical Support:

(Monday through Friday, 8:00 a.m. to 8:00 p.m. Eastern Time).
Within the United States: 1-800-GEFANUC (1-800-433-2682)
Option 3 for Support
International: 1-434-978-5100
Option 2 for Support
135
GE9 OPC Server
Support for the Process Hardware
By World Wide Web
. Click the shortcut to visit the GE Fanuc web site.
By Phone
1-800-433-2682
136
Creating Custom Client Applications
The I/O Server is an OLE application that you can control programmatically. It exposes its
functionality to other OLE applications through its interfaces, which means you can create custom
OLE applications to access or control the driver.
For example:
• You can use Visual Basic to programmatically enable channels, device, or datablocks
depending on user input.
• You can use VBA in Excel to create a program that generates reports comparing device
statistics within a driver.
• You can write programs that control the driver with higher performance using C or C++.
Refer to the following topics for steps on getting started with creating custom applications:
• Creating a Custom Application Using Microsoft Visual Basic
• Creating a Custom Application Using C or C++
• Accessing GE9 Server Data Using an OPC Client
Creating a Custom Application Using Microsoft Visual Basic

Microsoft Visual Basic is one of many applications that you can use to develop custom OLE
applications for use with the GE9 I/O driver.
To start designing a Visual Basic application that accesses the GE9 I/O driver objects:
1. Start Visual Basic and select References from the Projects menu. The GE Fanuc GE9DRV
OPC Server 7.10 Library should display in the Available References list box. If it does, select
it. If it does not, browse your directories for .TLB files and add GE9DRV.TLB to the
Available References list box.
2. Select Object Browser from the View menu and select GE9DRV from the Libraries/Projects
drop-down list at the top of the browser.
3. Select Help on the Properties and Methods to learn how to use the driver objects for creating
your application.
The type library, GE9DRV.TLB, is installed in the same path that you installed the GE9 I/O Server.
NOTE: To use Visual Basic for Applications (VBA) instead of the VB Compiler, select References from
the Tools menu in step 1 and follow steps 2 and 3 above.
Creating a Custom Application Using C or C++

You can create a custom client application for use with the I/O Server using Microsoft Visual C or
C++.
137
GE9 OPC Server
To get started creating an client application with C or C++:
1. Add a call to CoCreateInstance to load the server and get a pointer to the driver interface.
2. Include InterfaceDef.h in the source from your driver.
3. Add Interfacedef_i.obj to the project.
You can obtain copies of InterfaceDef.h and Interfacedef_i.obj from GE Fanuc. Contact your local GE
Fanuc sales representative for more information.
Accessing GE9 Server Data Using an OPC Client

You can use any v1.0a OPC-compliant client to access data from your process hardware through the
GE9 OPC server using the GE9 driver. In order to access this data, your client must use the OPC
Custom interface to communicate with the GE9 OPC server. The GE9 OPC server does not support the
OPC Automation interface.
You can begin accessing OPC data from the GE9 OPC server by using the Power Tool to enter the
default driver configuration file name for the server. To learn how to enter this information, refer to
Setting Defaults for the I/O Driver Configuration File Name and Path.
Use the following syntax for the OPC ItemID:
devicename:address (analog values)
devicename:address:bit (digital values)
For an explanation of this syntax, refer to Specifying I/O Addresses
If your OPC client supports browsing, you can also browse the GE9 OPC server.
138
Where to Find Information
Welcome to GE9 I/O driver online help! This help system provides all the information you need to use
the GE9 I/O driver. Click one of the links below to learn more about the features of the GE9 online
help:
• Accessing Information
• Navigating in the Online Help
• Customizing the Online Help
• Using the Help Menus
• Printing the Online Help
Accessing Information
The GE9 I/O driver online help consists of independent topics with specific information on I/O driver
concepts and procedures. You can access these topics using one of the following methods:
• F1 help
• The index
• The full-text search
• The table of contents
The index, full-text search, and table of contents are all located in the Help Topics dialog box. You can
display this dialog box by using one of the following methods:
• Selecting Help Topics from the Power Tool’s Help menu.
• Selecting GE9 Help from the Start menu as follows:
1. Select Programs from the Start menu.
2. Select FIX, Dynamics, or iFIX from the Programs menu.
3. Select GE9 Help from the context menu.
Using F1 Help
The fastest way to get help using the Power Tool fields is by pressing the F1 key. To display F1 help,
select the field or control you want information on and press the F1 key. The topic that appears is
specific to the selected field or control and usually explains what happens when you enter information
in the field, which entries are valid, and provides examples of valid entries when applicable.
Using the Help Index

The online help provides an index to all its topics. This index is similar to the index in a printed book.
139
GE9 OPC Server
To search the index:
1. Select the Index tab in the Help Topics dialog box.

2. Type or select the word you want information on.
3. Double-click the indexed item in the lower part of the Index tab to display the associated
topic. If the word you entered is associated with more than one topic, a list box appears
displaying all the topics indexed under the word you entered.
4. Double-click the topic you want to display.
Using the Help Full-Text Search

If you can’t find the information you’re looking for in the index, you can use the full-text search
capability. A full-text search finds every occurrence of a selected word or phrase anywhere within the
online help.
To use the full-text search:
1. Select the Find tab in the Help Topics dialog box.

2. Follow the prompts for creating the word list for the Help file.
3. Enter the word or phrase you want to locate in lower case text.
4. Double-click the associated topic you want to display from the list at the bottom of the Find
tab.
NOTE: Do not enter your search string with all upper case text. Using upper case text locates only
words and phrases in upper case. Using lower case text, on the other hand, finds all matching words
and phrases.
Using the Help Table of Contents

The table of contents provides an overview of what’s available in the GE9 online help. It displays the
titles of the books and the topics within each book.
To use the Table of Contents:
1. Select the Contents tab in the Help Topics dialog box.

2. To open a book, double-click it.
3. Double-click the topic you want to read.
4. To close a book, double-click it again.
Navigating in the Online Help

When you access a topic in the GE9 I/O driver online help, it may not provide all the information you
need. To learn more about a topic, you can:
• Use the Help Button Bar.
140
GE9 OPC Server
• Use help links.
Using the Help Button Bar
The button Lets you...
Help Topics Display the Help Topics dialog box.
Back Return to the last topic you viewed. The default keyboard shortcut is
CTRL + B. You can also see a list of previously viewed topics by
selecting Display History Window in the Options Menu. Refer to Using
the Help Menus for details on GE9 Help menu commands.
Print Print the current topic. See Printing the Online Help for information on
how to print the entire help system.
Using Help Links

Green words or phrases are links. Clicking a link either displays another topic or a pop-up window on
top of the current topic. If you are using the keyboard, press the Tab key to move to the next link in the
topic and press the Enter key to activate the link.
Links to other topics are green with a solid underline and are called jumps. Jumps take you out of
viewing the current topic to viewing a new topic. Links that display pop-up windows are green with a
dotted underline. Pop-up windows display over the current window and are usually definitions of
terms.
Using the Help Menus

The following menus appear at the top of every Help topic:
Each menu contains a list of commands. To display the commands, click the menu name. The
following table explains the function of each command.
Menu Command Description
File
Open Opens another help file.
Print Topic Prints the currently displayed topic.
Exit Exits the GE9 online help.
141
GE9 OPC Server
Menu Command Description
Edit
Copy Copies the selected text.
Annotate Makes an annotation to a topic. When you select this command, a dialog
box appears with a space for entering your annotation.
Help inserts a green paperclip icon at the top, left corner of the topic to
indicate that an annotation exists for the topic. To view an annotation,
click the green paperclip. Annotations remain with topics after you exit
and re-open the online help.
Bookmark
Define Bookmarks topics for reference during a Help session.
Options
Keep on Top Chooses whether to display the GE9 I/O driver help on top of all open
applications or to cover the GE9 help as other applications open.
Display History Displays all the topics you have viewed during a Help session.
Window
Font Lets you choose the font size used by the online help.
Use System Colors Directs the online help to use the system colors of your computer.
Help
Version Displays the version of the GE9 I/O driver online help.
Customizing the Online Help

The GE9 online help lets you annotate and bookmark topics.
Annotations
Select the Annotations command from the GE9 Help Edit menu to add your own annotations to a
topic.
142
GE9 OPC Server
Bookmarks
Select the Define command from the Bookmark menu to mark the topics that you want to refer back to
during a Help session.
Refer to the Microsoft Windows Help for details on making annotations and bookmarks.
Printing the Online Help
To print one GE9 Help topic at a time:
• Click Print from the Help Button Bar.
To print the entire online help as a book:
1. Open the Help Topics dialog box and select the Contents tab.
2. Double-click the Print Version book.
3. Double-click the GE9 Help Print Version topic.
4. Click Print from the Help Button Bar to print the entire help system.
143
Glossary
The following terms are used in the I/O Driver Power Tool.
• CSV File
• Exception-based Processing
• I/O Address
• I/O Driver
• NODE:TAG.FIELD
• Primary Database Blocks
• Process Database
• Process Database Block
• Run-time Configuration File
• SAC
• Signal Conditioning
• SIM Driver
• Time-Based Scan Time
CSV File
A comma separated file that the I/O Driver Power Tool creates when it exports a configuration file.
Comma separated files can be edited in any third-party application that supports CSV files, such as
Microsoft® Excel™ or a text editor. Comma separated value files can also be created in a third-party
application and read by the I/O Driver Power Tool.
Exception-based Processing
SAC can perform exception-based processing on the following events:
• The datablock changes in common memory.
• Unsolicited messages from the process hardware.
• Operator actions.
• Instructions from software applications.
I/O Address
A location in the process hardware (for example, a register, address, or point) that the driver reads from
and writes data to. An I/O address is a portion of a datablock.
145
GE9 OPC Server
I/O Driver
The software interface responsible for sending data to and acquiring data from the process hardware.
When discussing OPC drivers, the term I/O Server is sometimes used as well.
NODE:TAG.FIELD
NODE:TAG.FIELD is a tagname in FIX applications. It provides the information needed to access
database data.
NODE: defines the computer where the data you require is located. This can be the computer you are
working on or a remote computer.
TAG: is the name of a database block. Block names can be up to 30 characters long.
FIELD: defines the data type.
Primary Database Blocks

Primary database blocks are blocks in the process database that communicate with field devices.
Process Database
The process database is a representation of your process stored in memory. The process database is
made up of process database blocks (tags). Database blocks are units of instruction assigned to perform
process functions. Examples of process functions are: comparing process values against alarm limits,
performing calculations based on process values, and writing values to the process hardware.
Process Database Block

Individual units of instructions that receive, verify, manipulate, and output process values. Process
database blocks can also compare a process value against an alarm limit and perform calculations
based on a specific process value.
Run-time Configuration File

The process control software uses run-time configuration files (.GE9 files) to communicate with the
process hardware at run-time.
SAC
The Scan, Alarm, and Control program (SAC) is a FIX system task that runs on a SCADA server. SAC
transmits and receives data back and forth between the process database and the I/O driver’s common
memory.
SAC performs the following tasks:
146
GE9 OPC Server
• Fetches data from the I/O driver’s common memory.

• Translates the data into the format expected by the process database.
• Checks the data against the alarm limits and generates alarm messages.
• Executes the control logic.
• Detects exceptions.
• Makes requested writes to the driver’s common memory.
Signal Conditioning
The method by which a raw process data value is scaled.
SIM Driver
An I/O driver used to simulate input and output of the process database for FIX applications. SIM
values are saved in the process database itself but are cleared when SAC is started or when you reload
the process database. SIM registers range from 0 to 2000 for analog values and 0:0 to 2000:15 for
digital values.
Time-Based Scan Time

With a time-based scan time, SAC retrieves data at set time intervals. Use time-based scanning when
your data changes frequently.
147
Appendices
The following statistics are covered in the appendices:
• Channel Statistics
• Datablock Statistics
• Device Statistics
• I/O Driver Statistics
Appendix A: Channel Statistics

The following channel statistics are described in this section:
• Channel Statistics: Active Queue Count
• Channel Statistics: Number of Datablocks
• Channel Statistics: Number of Devices
• Channel Statistics: Errors
• Channel Statistics: Overruns
• Channel Statistics: Parse Queue Count
• Channel Statistics: Read Count Max
• Channel Statistics: Read Queue Count
• Channel Statistics: Receives
• Channel Statistics: Retries
• Channel Statistics: Timeouts
• Channel Statistics: Transmits
• Channel Statistics: Write Queue Count
Channel Statistics: Active Queue Count

Displays the number of messages that have been recently transmitted on the channel to the process
hardware and are waiting for a response.
Channel Statistics: Number of Datablocks

Displays the number of datablocks configured on all the devices for the selected channel.
Channel Statistics: Number of Devices

Displays the number of devices configured for the selected channel.
149
GE9 OPC Server
Channel Statistics: Errors

Displays the total number of protocol errors that were sent from the process hardware and received on
the selected channel.
Protocol errors occur when:
• The process hardware receives a message with a checksum error. Typically, interference or a
loose connection can cause checksum errors.
• The driver requests data from a register that does not exist in the process hardware.
For more information on the cause of the error, examine the Last Error field in the datablock statistics.
Channel Statistics: Overruns

Displays the total number of overruns for the channel. An overrun occurs when the driver attempts to
read more data from the hardware than it can process at one time. A high number of overruns indicate
that your driver is poorly configured for its environment and, as a result, your data is not updating at
the specified poll rate.
Any of the following conditions can cause overruns:
• Bandwidth saturation on your network.
• Turnaround delays in the PLC.
• Overflowing message queues in the process hardware.
To understand how overruns occur requires a little knowledge of how the driver reads data. When a 7.x
driver requires data for a datablock, it places a read request into its read queue. When the driver
processes this request, it sends a message to the process hardware for data.
The driver reads (polls) each datablock according to its poll rate. Each time the poll rate expires, the
driver creates a read request for that datablock. If a read request for a datablock is still pending in the
read queue when the driver issues another read request, an overrun occurs. The driver discards the
second message since a request for the same data is already pending.
Example
Poll Rate = 1 second

Assume that at this setting, the driver can poll 5 datablocks on the device per second. If you configure
10 datablocks for the device, all 10 try to poll at the same time. In the first second, the first 5 poll
leaving 6 to 10 still pending. The following figure shows what happens next.
150
GE9 OPC Server
You can prevent overruns by phasing datablocks. Refer to Using Phasing with Poll Rates for details on
phasing datablocks.
NOTE: Setting the poll rate to zero forces the driver to run at its maximum rate and disables the
overrun statistics counter. Set the poll rate equal to 0 if it is more important to run the driver at its
maximum speed than to detect overruns.
Channel Statistics: Parse Queue Count

Displays the number of responses that are waiting for a datablock to parse them.
Channel Statistics: Read Count Max

Displays the maximum number of pending messages since the driver was started.
Channel Statistics: Read Queue Count

Displays the number of read requests that are pending for the channel.
151
GE9 OPC Server
Channel Statistics: Receives

Displays the total number of messages received on the channel from the process hardware. The
Receives field includes both valid and invalid messages. Use the Errors field to view the number of
invalid messages.
Channel Statistics: Retries

Displays the total number of messages re-sent to the process hardware because of errors. A value in the
Retries field does not indicate a communication problem. It may, for example, indicate that the process
hardware is slow replying to driver requests.
Retries are a timing property that you set for each device. The driver uses the value you enter to
determine how many times to re-send a request after a timeout occurs. Possible reasons for the driver
timing out include:
• Checksum errors from communication line interference.
• Busy PLCs. PLCs may not reply if they are involved in another task.
• Hardware problems such as a faulted PLC. The hardware cannot recover unless you clear the
fault.
• A reply timeout that is too low.
For an explanation of how the Retries property works, refer to Setting Device Timing Properties:
Reply Timeout, Retries, and Delay Time.
Channel Statistics: Timeouts

Displays the total number of messages sent to the process hardware from the selected channel that did
not receive a reply.
Timeouts result from the device property, Reply Timeout. This property specifies the length of time
that the I/O driver waits for a response from the process hardware. If the driver sends a message to the
hardware and does not receive a response within the specified reply timeout, a timeout occurs and the
value in the Timeouts field increments.
If you have a high timeout count:
1. Try increasing the value for the Reply Timeout property.

2. Examine your cable. You may have a bad connection.
3. Verify that your channel properties match the process hardware. If you don't know your
hardware settings, refer to your process hardware documentation.
4. Examine the Last Error field in the datablock statistics for a possible cause of your timeouts.
For an explanation of how the Reply Timeout property works, refer to Setting Device Timing
Properties: Reply Timeout, Retries, and Delay Time.
Channel Statistics: Transmits

Displays the number of messages sent to the process hardware from the selected channel.
152
GE9 OPC Server
Example
Number of devices configured for the driver = 4

Number of messages sent on Device1 = 30
Total number of messages sent = 75
Transmits field displays: 75
Channel Statistics: Write Queue Count

Displays the number of write requests that are pending for the channel.
Appendix B: Datablock Statistics

The following datablock statistics are described in this section:
• Datablock Statistics: Block Write Queue Count
• Datablock Statistics: Data Quality
• Datablock Statistics: Errors
• Datablock Statistics: Last Error
• Datablock Statistics: Last Error Time
• Datablock Statistics: Last Read Time
• Datablock Statistics: Last Write Time
• Datablock Statistics: Overruns
• Datablock Statistics: Receives
• Datablock Statistics: Retries
• Datablock Statistics: Timeouts
• Datablock Statistics: Transmits
Datablock Statistics: Block Write Queue Count

Displays the number of writes pending for the selected datablock when the Block Write option is
enabled. If this option is disabled, the value in this field is zero. If you enable the Block Write option
and subsequently disable it, all pending writes are discarded and the value of the field is set to zero.
Datablock Statistics: Data Quality

Displays the quality of the data in the datablock.
153
GE9 OPC Server
Datablock Statistics: Errors

Displays the total number of protocol errors that were sent from the process hardware and received by
the selected datablock.
For more information on the cause of the error, examine the Last Error field for the datablock.
Datablock Statistics: Last Error

Displays the last error received by the datablock from the process hardware. Errors displayed in this
field are specific to the hardware. The GE9 I/O driver does not provide information for this field.
Datablock Statistics: Last Error Time

Displays the last time and date that an error occurred for the selected datablock.
Datablock Statistics: Last Read Time

Displays the last time and date that the I/O driver successfully read data from the selected datablock.
Datablock Statistics: Last Write Time

Displays the last time and date that the driver successfully wrote data to the selected datablock.
Datablock Statistics: Overruns

Displays the total number of overruns for the datablock. An overrun occurs when the driver attempts to
154
GE9 OPC Server
Example

phasing datablocks.
Datablock Statistics: Receives

Displays the total number of messages the datablock received from the process hardware. The
Receives field includes both valid and invalid messages. Use the Errors field to view the number of
invalid messages.
155
GE9 OPC Server
Datablock Statistics: Retries

timing out include:
fault.
Datablock Statistics: Timeouts

Displays the total number of messages sent to the process hardware from the selected datablock that
did not receive a reply.

4. Examine the Last Error field for a possible cause of your timeouts.
Datablock Statistics: Transmits

Displays the number of messages sent to the process hardware from the selected datablock.
Appendix C: Device Statistics

The following device statistics are described in this section:
• Device Statistics: Callback Received
• Device Statistics: Clear To Send
• Device Statistics: Connection Count
156
GE9 OPC Server
• Device Statistics: Connection Failed

• Device Statistics: Connection Status
• Device Statistics: Errors
• Device Statistics: Initialization Needed
• Device Statistics: Last Queue Sent
• Device Statistics: Number of Datablocks
• Device Statistics: Outstanding Messages
• Device Statistics: Overruns
• Device Statistics: Read Queue Count
• Device Statistics: Receives
• Device Statistics: Retries
• Device Statistics: TCP Status
• Device Statistics: Timeouts
• Device Statistics: Transmits
• Device Statistics: Write Queue Count
Device Statistics: Callback Received

Displays whether the driver received a callback message from the current device.
Value in Field Meaning
0 False; no callback was received.
1 True; a callback was received.
Device Statistics: Clear To Send

Displays if the driver is ready to send a message to the current device.
0 False; the driver is not ready to send any messages; one or more
messages are pending.
1 True; the driver is ready to send a message.
Device Statistics: Connection Count

Displays the number of TCP connections the device has made.
157
GE9 OPC Server
Device Statistics: Connection Failed

Displays if the connection to the current device failed.
0 False; the connection to the current device is operating correctly.
1 True; the connection to the current device has failed.
Device Statistics: Connection Status

Displays the connection status of the GE9 driver.
0 Not connected.
2 Connected.
Device Statistics: Errors

Displays the total number of protocol errors that were sent from the process hardware and received by
the selected device.
Device Statistics: Initialization Needed

Displays when the driver needs to perform its initialization logic.
0 False; the driver is initialized.
1 True; the driver is either starting up or lost and subsequently restored its
connection to the current device. In both cases, the driver needs to be
initialized.
158
GE9 OPC Server
Device Statistics: Last Queue Sent

Displays the queue of the last message sent to current device.
0 The last message was sent from the Read queue.
1 The last message was sent from the Write queue.
2 The last message was sent from the Active queue.
99 No message was sent. This value is displayed while the driver initializes.
Device Statistics: Number of Datablocks

Displays the total number of datablocks configured for the selected device.
Device Statistics: Outstanding Messages

Displays the number of messages sent to the process hardware and that are pending in the PLC’s
memory buffer waiting to be processed.
The maximum number of outstanding messages is equal to the value in the Simultaneous Messages per
Device field. To access this field:
Device Statistics: Overruns

Displays the total number of overruns for the device. An overrun occurs when the driver attempts to
159
GE9 OPC Server
Example

phasing datablocks.
160
GE9 OPC Server
Device Statistics: Read Queue Count

Displays the number of read requests currently pending for the device.
Device Statistics: Receives

Displays the total number of messages the device received from the process hardware. The Receives
field includes both valid and invalid messages. Use the Errors field to view the number of invalid
messages.
Device Statistics: Retries

Retries field for a device does not indicate a communication problem. It may, for example, indicate
that the process hardware is slow replying to driver requests.
timing out include:
fault.
For an explanation of the Retries property works, refer to Setting Device Timing Properties: Reply
Timeout, Retries, and Delay Time.
Device Statistics: TCP Status

Displays the status of the TCP/IP connection.
1 Fully connected; ready to read and write data.
2 Not connected.
3 Connection in progress.
4 Connection failed.
5 TCP connection but no session is established. When a session is

established, the connection status becomes fully connected.
161
GE9 OPC Server
Device Statistics: Timeouts

Displays the total number of messages sent to the process hardware from the selected device that did
not receive a reply.

Device Statistics: Transmits

Displays the number of messages sent to the process hardware from the selected device.
Example
Number of datablocks configured for the driver = 2

Number of messages sent from DataBlock1 = 30
Number of messages sent from DataBlock2 = 30
Device Statistics: Write Queue Count

Displays the number of write requests currently pending for the device.
Appendix D: I/O Driver Statistics

The following I/O driver statistics are described in this section:
• I/O Driver Statistics: Driver Name
• I/O Driver Statistics: Errors
• I/O Driver Statistics: Number of Channels
• I/O Driver Statistics: Number of Datablocks
• I/O Driver Statistics: Number of Devices
• I/O Driver Statistics: Overruns
162
GE9 OPC Server
• I/O Driver Statistics: Receives

• I/O Driver Statistics: Retries
• I/O Driver Statistics: Timeouts
• I/O Driver Statistics: Transmits
Driver Name
Displays the I/O driver acronym, name, and version number.
I/O Driver Statistics: Errors

Displays the total number of protocol errors sent from the process hardware.
Number of Channels
Displays the number of channels configured for the driver.
Number of Datablocks
Displays the total number of datablocks configured for all devices on all driver channels.
Number of Devices
Displays the total number of devices configured on all driver channels.
I/O Driver Statistics: Overruns

Displays the total number of overruns. An overrun occurs when the driver attempts to read more data
from the hardware than it can process at one time. A high number of overruns indicate that your driver
is poorly configured for its environment and, as a result, your data is not updating at the specified poll
rate.
163
GE9 OPC Server
Example

phasing datablocks.
164
GE9 OPC Server
I/O Driver Statistics: Receives

Displays the total number of messages received from the process hardware. The Receives field
includes both valid and invalid messages. Use the Errors field to view the number of invalid messages.
I/O Driver Statistics: Retries

timing out include:
fault.
I/O Driver Statistics: Timeouts

Displays the total number of messages sent to the process hardware that did not receive a reply.

I/O Driver Statistics: Transmits

Displays the total number of messages sent to the process hardware on all channels.
165
GE9 OPC Server
Example
Number of channels configured for the driver = 2

Number of messages sent on Channel1 = 560
Number of messages sent on Channel2 = 220
166
Index
! address length ......................... 63, 70, 73, 75, 111
!MODE ............................................................. 80 addressing format in Database Builder ............ 80
!POLL............................................................... 80 addressing format in the Power Tool ............... 63
!SEND ................................................ 14, 80, 123 advanced settings ..................................43, 45, 46
!SWITCH ......................................................... 80 Alarm History .................................................130
1 auto create........................................................ 45
12AL signal conditioning ................................. 85 automatic datablock creation ............................. 6
12BN signal conditioning ................................. 85 automatic server connection ............................ 53
13AL signal conditioning ................................. 86 automatic startup ........................ 43, 45, 105, 130
13BN signal conditioning ................................. 87 B
15AL signal conditioning ................................. 88 backup channels..............................................123
15BN signal conditioning ................................. 89 backup devices
3 delay time .................................................... 59
32KA signal conditioning................................. 90 retries ........................................................... 60
32KB signal conditioning ................................. 91 backup devices................................................123
3BCD signal conditioning ................................ 91 backup IP address ............................................ 60
4 backup reply timeout ....................................... 60
4BCD signal conditioning ................................ 92 bad data...........................................................129
8 binary files ....................................................... 99
8AL signal conditioning ................................... 93 block write queue............................................153
8BN signal conditioning ................................... 94 block writes ........................................14, 72, 153
9 browser ............................................................ 33
90-30 PLC ........................................................ 22 C
90-70 PLC ........................................................ 23 C++ custom client applications ......................137
A cabling ............................................................. 19
access time............................ 65, 66, 69, 118, 129 changing servers .............................................. 49
accessing documentation ................................ 139 channels
accessing GE9 data ......................................... 138 active queue count ......................................149
accessing the Power Tool ................................. 31 adding .......................................................... 41
active queue count statistics ........................... 149 demand polling ...........................................117
adding channels .......................................... 41, 56 description ................................................... 56
adding datablocks ....................................... 41, 63 disabling ...............................................10, 123
adding devices ............................................ 41, 57 enabling ..........................................10, 57, 123
GE9 OPC Server
errors........................................................... 150 configuring DCOM......................... 116, 119, 121

name ............................................................. 57 configuring devices.......................................... 57
number of ................................................... 163 configuring drivers
number of datablocks ................................. 149 from custom applications............................... 7
number of devices....................................... 149 remotely ............................................8, 50, 116
overruns ...................................................... 150 configuring drivers .......................................... 40
parse queue count ....................................... 151 configuring drivers .......................................... 41
pending messages ....................................... 151 configuring drivers .......................................... 55
polling......................................................... 117 configuring drivers .......................................... 55
properties ................................................ 56, 57 configuring drivers .......................................... 68
read queue count ......................................... 151 configuring drivers .......................................... 77
received messages ...................................... 152 configuring drivers .......................................... 78
retries .......................................................... 152 configuring drivers .......................................... 78
statistics .............. 103, 149, 150, 151, 152, 153 configuring drivers .......................................... 96
switching .................................................... 123 configuring local communication .................... 49
timeouts ...................................................... 152 configuring remote communication ....49, 50, 116
transmitted messages .................................. 152 configuring the hardware ................................. 19
viewing statistics ........................................ 103 configuring the Power Tool ........ 8, 40, 41, 42, 55
write queue count ....................................... 153 Connect button................................................. 70
checking communication ................................ 109 connecting to local servers.............. 38, 40, 49, 50
checksum error statistics......... 150, 154, 158, 163 connecting to remote servers .. 38, 40, 49, 50, 116
choosing commands ......................................... 34 connection count .............................................157
command line parameters ................................. 53 connection status.............................................158
communicating locally ..................................... 49 connection timeout .......................................... 45
communicating remotely .................... 49, 50, 116 creating custom applications using C or C++ .137
communication errors ....................................... 10 creating custom applications with Visual
Basic ...........................................................137
conditioning data .............................................. 82
creating custom client applications .................137
Configuration button ........................................ 40
creating datablocks automatically from
configuration file default settings ..................... 75
client applications .......................................... 6
configuration file name............................... 43, 72
creating datablocks in FIX Database Builder . 96,
configuration file path ................................ 43, 72 117
configuration methods ...................................... 55 creating datablocks with FIX ........................... 77
Configuration mode .......................................... 31 creating new files ........................................36, 40
Configuration toolbar ....................................... 41 creating reports .........................................99, 117
configuring channels ........................................ 56 CSV files ..................................................99, 117
configuring datablocks ..................................... 63 custom applications ........................................... 7
configuring datablocks automatically ................. 6 custom client applications...............................137
168
GE9 OPC Server
customizing help............................................. 142 saving..............................................96, 98, 117

D statistics ...................... 103, 153, 154, 155, 156
data quality ..................................................... 153 timeouts ......................................................156
data scope ................................................... 15, 38 transmitted messages ..................................156
Data scope button ............................................. 40 verifying ...................................................... 96
data types .......................................................... 70 viewing statistics.........................................103
database block links.......................................... 73 datablocks .......................................................123
database blocks ........................................... 72, 78 date stamp for data and alarms ........................ 12
datablock addresses .......................................... 63 DCOM ............................................ 116, 119, 121
datablocks deadband .......................................................... 72
adding ..................................................... 41, 63 decreasing unnecessary stress .........................112
addresses........................................... 70, 73, 75 default configuration file name .............31, 43, 72
block write queue count.............................. 153 default configuration file path ..............31, 43, 72
block writes .................................................. 14 default settings ......................................72, 75, 96
creating automatically in Database delay time property ...............................58, 59, 61
Builder .................................................. 6, 96
demand polling ...............................................117
creating with FIX applications ..................... 77
devices
data quality ................................................. 153
adding .....................................................41, 57
data types ...................................................... 70
configuring the hardware ............................. 19
demand polling ........................................... 117
connection count .........................................157
description .................................................... 71
connection status.........................................158
disabling ............................................... 10, 123
demand polling ...........................................117
eliminating extra ones................................. 112
description ................................................... 61
enabling .......................................... 10, 71, 123
disabling ...............................................10, 123
errors........................................................... 154
enabling ..........................................10, 61, 123
last error received ....................................... 154
errors ...........................................................158
last error time.............................................. 154
IP address..........................................57, 60, 62
last successful read time ............................. 154
modifying .................................................... 57
last successful write time ............................ 154
multiple messages ........... 15, 46, 112, 124, 131
modifying ..................................................... 63
name ............................................................ 61
name ............................................................. 70
number of............................................149, 163
number of ................................... 149, 159, 163
number of datablocks..................................159
overruns ...................................................... 154
overruns ......................................................159
polling......................................................... 117
polling .........................................................117
properties ..... 63, 65, 66, 67, 69, 70, 71, 72, 73,
properties .............................. 57, 58, 60, 61, 62
74, 75
received messages.......................................161
received messages ...................................... 155
setting up address......................................... 57
retries .......................................................... 156
169
GE9 OPC Server
statistics .............. 103, 157, 158, 159, 161, 162 running as a service ..............................12, 121
switching .................................................... 123 selecting an account to run as a service ....... 12
TCP status................................................... 161 setting up ................................................17, 38
timeouts .............................................. 161, 162 starting .............................. 40, 50, 70, 104, 133
transmitted messages .................................. 162 statistics ................ 44, 103, 132, 133, 163, 165
viewing statistics ........................................ 103 stopping ................................ 40, 107, 125, 133
diagnostics ........................................................ 15 timeouts ......................................................165
differences between 6.x and 7.x drivers ........... 24 transmitted messages ..................................165
disabling block writes ....................................... 72 uninstalling .................................................. 26
disabling channels .................................... 10, 123 upgrading ................................................26, 27
disabling datablocks ................................. 10, 123 viewing statistics.........................................103
disabling devices ...................................... 10, 123 DRVST ...........................................................132
disabling outputs....................................... 72, 116 E
disabling writes............................................... 116 Edit menu....................................................34, 35
Display Mode menu ................................... 34, 35 editing configurations .....................................117
documentation ........................................ 139, 140 eliminating extra datablocks ...........................112
driver messages 43, 116, 125, 126, 127, 130, 133 enabling block writes ....................................... 72
driver name ..................................................... 163 enabling channels ...............................10, 57, 123
driver not communicating............................... 126 enabling datablocks ............................10, 71, 123
driver stops unexpectedly ............................... 130 enabling devices .................................10, 61, 123
drivers enabling outputs...................... 57, 61, 71, 72, 116
alarms ................................................... 12, 130 end address .........................................63, 73, 111
architecture ..................................................... 3 entering driver information in FIX Database
Builder ......................................................... 78
configuration .. 7, 8, 40, 41, 55, 68, 77, 78, 116
error numbers.................. 125, 126, 128, 132, 133
configuring remotely ............................ 50, 116
error statistics.......................... 150, 154, 158, 163
error numbers ..................................... 126, 132
Ethernet .......................................... 20, 22, 23, 24
error statistics ............................................. 163
Event Viewer .................................. 125, 133, 134
features ........................................................... 5
exception-based database blocks ..................... 72
how they work ................................................ 3
exception-based processing ..........................9, 72
installing ....................................................... 27
excess datablocks............................................112
manual start-up ........................................... 106
F
overruns ...................................................... 163
F1 help ............................................................139
pending messages ....................................... 151
features .............................................................. 5
poll rate ......................................................... 74
File menu ....................................................34, 36
received messages ...................................... 165
file name .......................................................... 72
remote configuration ...................................... 8
file path ............................................................ 43
retries .......................................................... 165
170
GE9 OPC Server
finding information................................. 139, 140 I

FIX ................................................................. 123 I/O address format ........................................... 80
FIX applications ...... 6, 72, 77, 78, 79, 80, 95, 96, I/O driver statistics..........................................125
98, 106, 107
I/O Server ...............................................3, 49, 53
FIX Database Builder
index ...............................................................139
addressing format ......................................... 80
information .............................................139, 140
verifying datablocks created from ................ 96
installing a 7.x driver ....................................... 27
FIX Database Builder ....................... 6, 77, 78, 79
Interfacdef_i.obj .............................................137
FIX Database Builder ....................................... 82
InterfaceDef.h .................................................137
IOCNTRL .......................................................126
IP address..............................................57, 60, 62
L
last error statisitcs ...........................................154
FIX Database Builder ..................................... 109
last error time statistics ...................................154
FIX path.......................................................... 130
last read time statistics ....................................154
FIXIOUser Account ......................................... 12
last write time statistics...................................154
fluctuations in data ........................................... 72
latched data .................................................11, 73
format for I/O addresses ................................... 80
length ........................................................70, 111
full text search ................................................ 140
LIN signal conditioning ................................... 84
G
loading drivers ........................................126, 129
GE9 I/O driver features ...................................... 5
local communication........................................ 49
getting technical support................................. 135
local connection ............................................... 49
glossary........................................................... 145
local server............................................49, 50, 70
graphical user interface....................................... 8
local server connection .................................... 38
H
logging messages ....................................125, 133
handling exceptions ............................................ 9
M
hardware ............................................... 18, 19, 24
main toolbar ..................................................... 40
hardware errors ............................................... 154
making new files.............................................. 40
hardware options ........................................ 70, 95
manual start-up ...............................................106
help ......................................................... 124, 139
maximum memory size ................................... 43
Help menu .................................................. 34, 37
maximum messages per device . 15, 46, 112, 124,
help menus...................................................... 141 131
help printing ................................................... 143 maximum outstanding messages ..................... 43
help topics ........................................................ 37 memory growth increment ............................... 43
HOSTS file ....................................................... 57 menu bar ............................. 34, 35, 36, 37, 38, 39
how the driver works .......................................... 3 message length................................................111
how to use the driver ...................................... 115 message log ............................................125, 133
171
GE9 OPC Server
messages ................................. 116, 125, 127, 130 optimization techniques ..........................111, 112
messages not being transmitted ...................... 127 optimizing your system ..........................111, 112
Mission Control .............. 106, 107, 125, 132, 133 Options menu..............................................34, 38
modifying channels .......................................... 56 overrun buffer .................................................. 43
modifying configurations ............................... 111 overrun statistics ..................... 150, 154, 159, 163
modifying datablocks ....................................... 63 overruns ..........................................................129
modifying devices ............................................ 57 P
multiple messages............... 15, 46, 112, 124, 131 parse queue count statistics .............................151
N path to configuration files ................................ 43
naming a channel .............................................. 57 path to configuring files ................................... 72
naming a datablock ........................................... 70 path to error resource DLL .............................. 43
naming a device ................................................ 61 path to signal conditioning DLL ...................... 43
navigating in the GE9 Help system ................ 140 pending messages ...........................................151
Network list box ............................................... 50 performance ............................................111, 112
New command .................................................. 36 phasing.................................... 10, 65, 67, 73, 129
new files ..................................................... 36, 40 ping .............................................................24, 57
Next Channel .................................................. 132 poll rate ......................... 9, 10, 65, 69, 73, 74, 115
NO_DATA ..................................................... 118 poll time ..........................................................118
nodename.GE9 ................................................. 43 polling devices ........................................117, 118
NONE signal conditioning ............................... 83 Power Tool
not receiving messages ................................... 127 addressing format ........................................ 63
number of channels ........................................ 163 browser ........................................................ 33
number of datablocks ..................... 149, 159, 163 configuring ....................... 8, 40, 41, 42, 43, 55
number of devices .................................. 149, 163 opening ................................... 50, 70, 104, 117
O options ......................................................... 38
old data ........................................................... 129 setup............................................................. 43
OLE for Process Control .................................... 5 starting ................................................104, 117
OLE server status bar ...................................................... 39
connecting to ................................................ 38 Power Tool ........................................................ 3
OLE server button ............................................ 40 Power Tool ...................................................... 31
OPC client ...................................................... 138 Power Tool ...................................................... 32
OPC servers ........................................................ 5 Power Tool ...................................................... 34
Open command................................................. 36 primary IP address ........................................... 62
opening files ............................................... 36, 40 primary poll rate .................................66, 74, 118
opening menus.................................................. 34 printing GE9 documentation...........................143
opening the Power Tool....... 40, 50, 96, 104, 117, printing help....................................................143
125, 130, 133
process hardware ..................................18, 19, 24
172
GE9 OPC Server
programming hardware .................................... 24 saving datablocks......................................98, 117

protocol errors ........................ 150, 154, 158, 163 saving files ............................................36, 40, 43
protocols ........................................................... 19 SCADA configuration ............................104, 105
Q scaling data ...................................................... 82
quality statistics .............................................. 153 scan time ......................................... 115, 118, 129
QuickFail logic ................................................. 10 SCU ........................................................104, 105
R searching help .................................................140
read count max ............................................... 151 secondary poll rate .................... 9, 65, 66, 74, 118
read queue count statistics .............................. 151 security ...................................................119, 121
received message statistics ..... 152, 155, 161, 165 sending multiple messages . 15, 46, 112, 124, 131
receiving old data ........................................... 129 server access ...........................................119, 121
receiving overruns .......................................... 129 server connection ........................................49, 53
refresh rate .................................................. 42, 44 server security .........................................119, 121
refreshing statistics ........................................... 44 service under Windows
refreshing the browser ...................................... 33 running the driver as .............................12, 121
remote communication ............... 49, 50, 116, 128 setting default values ..................................38, 75
remote configuration .......................................... 8 setting up drivers ........................................17, 38
remote connection .................................... 49, 128 setting up Power Tool options ......................... 38
remote control..................................................... 8 setting up security ...................................119, 121
remote machine name ....................................... 50 setting up the default configuration file path ... 43
remote machine's TCP/IP address .................... 50 setting up the Power Tool ................................ 42
remote server ........ 49, 50, 70, 116, 119, 121, 128 Setup dialog box ...................................31, 42, 43
remote server connection .................................. 38 short cut keys ................................................... 39
reply timeout property .......................... 58, 60, 62 signal conditioning ...... 82, 83, 84, 85, 86, 87, 88,
89, 90, 91, 92, 93, 94
reply timeout statistics ............ 152, 156, 162, 165
simulation mode ........................... 11, 43, 46, 124
report files ................................................ 99, 117
slow message rate ...........................................130
required software .............................................. 18
software ........................................................... 18
Reset button ...................................................... 40
specifying hardware options in FIX
resetting statistics ....................................... 38, 40
Database Builder.......................................... 95
retries property ..................................... 58, 60, 62
specifying I/O addresses in FIX Database
retry statistics .......................... 152, 156, 161, 165 Builder ......................................................... 80
running the driver as a service .................. 12, 121 specifying signal conditioning in Database
Builder ......................................................... 82
S
specifying the I/O driver in FIX Database
SAC ............................................................ 9, 105
Builder ......................................................... 79
Save As command ............................................ 36
start address ........................................63, 75, 111
Save command ................................................. 36
Start button ...................................................... 40
saving configuration changes ................... 98, 117
start polling ...........................................57, 61, 71
173
GE9 OPC Server
starting automatically in FIX .......................... 105 Tree Browser ................................................... 31

starting drivers ..... 40, 50, 70, 104, 105, 106, 125, troubleshooting ................... 24, 38, 124, 133, 134
130, 133
U
starting drivers from FIX ................................ 104
uninstalling a 6.x driver ................................... 26
starting drivers manually ........................ 104, 106
unused datablocks ...........................................112
starting the Power Tool .......................... 104, 117
upgrading the driver....................................26, 27
starting the Power Tool from FIX Database
user interface ..................................................... 8
Builder ........................................................ 117
using a logon account when running the
statistics ................ 15, 38, 44, 103, 125, 132, 133
driver as a service ........................................ 12
Statistics button ................................................ 40
using an OPC client ........................................138
Statistics mode .................................................. 31
using default driver settings ............................. 96
statistics refresh rate ................................... 42, 44
using drivers remotely ....................................... 8
status bar ........................................................... 39
using help..................................................37, 140
Stop button ....................................................... 40
using local servers ........................................... 50
stop polling ........................................... 57, 61, 71
using phasing with poll rates ........................... 67
stopping drivers ........................ 40, 107, 125, 133
using remote servers ........................................ 50
support .................................................... 124, 135
using the data scope ......................................... 38
supported hardware .......................................... 18
using the menus in help ..................................141
supported protocols .......................................... 19
using the Power Tool ..................................31, 32
supported signal conditioning ........................... 82
V
switching channels.................................... 80, 123
verifying datablocks created from Database
switching devices ..................................... 80, 123 Builder ......................................................... 96
system account ................................................. 12 View menu..................................................34, 39
system optimization ................................ 111, 112 viewing configuration properties ..................... 35
T viewing datablock statistics ............................103
table of contents.............................................. 140 viewing datablocks created from Database
Builder ......................................................... 96
TCP/IP
viewing error messages ..................................134
connection status ........................................ 161
viewing statistics ................................35, 40, 103
number of connections ............................... 157
Visual Basic custom applications ...................137
TCP/IP ...................................... 20, 22, 23, 24, 57
W
technical support..................................... 124, 135
Windows service
Templates dialog box ............... 31, 38, 40, 75, 96
running the driver as one ......................12, 121
time stamp for data and alarms ......................... 12
write messages ................................................116
timeout .............................................................. 45
write queue count statistics .............................153
timeouts .......................... 152, 156, 161, 162, 165
writing to a datablock ...............................14, 123
timing properties............................................... 58
Z
transceiver .................................................. 22, 23
zero poll rate ...................................................115
transmitted message statistics . 152, 156, 162, 165
174

Ge9 Opc Server

Uploaded by

Document Information

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

Ge9 Opc Server

Uploaded by

Copyright:

Available Formats

GE9 OPC Server

Disclaimer of Warranties and Liability

Version 7.19 – 06.05

• OLE Automation technology.

OLE Automation Technology

The I/O driver consists of the following OLE components:

Integration with the FIX

The I/O server consists of the following objects:

Exposes the data and functionality of the Server to other applications.

5. Common Memory DLL

7. Signal Conditioning DLL

8. I/O Driver Power Tool

9. OPC Server DLL

10. FIX Applications

11. OPC Client Applications

12. Automation Controller and COM Client Applications

13. Process Hardware

Any type of I/O device that controls a process.

Feature: Using the OLE for Process Control (OPC) Functionality

OLE for Process Control Standard defines:

Feature: Creating Datablocks Automatically in FIX Database Builder

Feature: Configuring the Driver from Custom COM/OLE Automation

Feature: Using the GE9 I/O Driver Graphical User Interface

Features of the Power Tool

• Runs as a stand-alone program or can be launched from FIX.

Feature: Remote Control and Configuration

To install the Power Tool for remote communication:

Feature: Using Exception-Based Processing

To configure a database block for exception-based processing:

Feature: Using Secondary Poll Rates

Feature: Phasing Poll Rates

Feature: Enabling or Disabling Individual Channels, Devices, and

• You want to use the datablock for output only.

Feature: QuickFail Logic

Reply Timeout = 05 (5 seconds)

Feature: Using Simulation Mode

Feature: Using Latched Data

Feature: Time/Date Stamp for Data and Alarms

Feature: Running as a Windows Service

the Stop button.

Registering the I/O Server as a Service

To register the I/O Server as a service:

1. Select Run from the Windows Start menu.

privileges to run the server as a service. To determine if the account has

Once you register the driver, complete these steps:

Feature: Block Writes

To send block writes through FIX:

1. Create a datablock with a maximum length of 99 words (198 bytes).

Feature: Advanced Diagnostics

To enable the data scope for a channel, device, or datablock:

Feature: Multiple Messages

To configure the driver to send multiple messages to a device:

1. Start the GE9 Power Tool.

1 Know your process hardware

What device does the driver communicate with?

What type of cable are you using?

What is the IP address for each device?

2 Choose the method of configuration

Choosing a Method for Configuring Your Driver

3 Configure the I/O driver

Adding and Modifying Channels

Adding and Modifying Devices

Adding and Modifying Datablocks