Proficy* Historian - GE Intelligent Platforms: Support Home

Proficy* Historian - GE Intelligent Platforms: Support Home

Getting Started with Historian

Using Historian with iFIX

You can enhance the power of the Historian by pairing it with iFIX. The benefits of using Historian with iFIX clients include:

• iFIX Chart features:

Sub-second support

Auto Update

Time Zone Support

Daylight Savings Time (DST) Support

Filter and Sort by description, and directly access OPC tags in the Expression Editor

Support for Historian interpolated data retrieval.

Ability to access multiple Historian Servers (even within the same chart).

The ability to easily script against the SDK in VBA. This allows you to retrieve record sets in

Historian for processing and display, and to build time-aware graphics that can display animations from any selected time.

Writing status information directly into iFIX tags, so the health of the iFIX Collector can be monitored in real time within iFIX.

Easy migration of iFIX Classic Historian Configuration and Data.

Easy migration of iFIX Alarm and Event Data.

Collection of iFIX Alarm and Event Data.

NOTE: You can plot any collected data, not just iFIX Collector data.

Please be aware of the following when using Historian with iFIX:

You must install iFIX before installing Historian if you want to install the iFIX Collector. If you attempt to install Historian on a machine without iFIX installed and select the iFIX Collector under the

Select Components, a message appears stating that iFIX is required on this node to install the iFIX

Collector.

You must install the iFIX Alarm & Event server before installing the iFIX AE Collector from the

Historian installation and setup program.

You must manually import the Historian Toolbar into the iFIX WorkSpace after you have installed

Historian. Refer to Importing the Historian Toolbar into iFIX for more information.

87

Proficy Historian Getting Started Guide

In working with iFIX, be aware that the Historian security is independent of iFIX security.

If you attempt to use the iFIX Chart Group Wizard to add Simulation or OPC tags, you will receive an error. The Chart Group Wizard only supports iFIX Historian tags that use the iFIX historical tag naming convention.

Historian does not support the installation of collectors or servers on Terminal Server machines running in application server mode.

Using iFIX drivers with Historian

If you are running iFIX in your Historian environment, you can use any iFIX driver (version 6.X or 7.X).

Historian uses data from the iFIX process database, therefore once the driver brings the data into the Process

Database (PDB), it is available to Historian via EDA and the iFIX Collector.

Collecting iFIX Alarm and Event Data

Historian supports Alarm and Event collection from an iFIX server.

To configure the iFIX AE collector to start automatically when iFIX starts add the iFIX AE collector to the list of startup tasks in the System Configuration Utility (SCU).

To add the collector to the SCU list, open the Task Configuration dialog box in iFIX, enter

ihIFIXAECollector.EXE in the Filename field and runasdos in the Command Line field, and click the Add button.

NOTES:

After starting the iFIX AE collector you will need to use the Historian administration tool to link it to

its associated iFIX data collector.

If ItemIDs are not being collected, and you see an entry in your log file that says "Alarm Item IDs Will

Not Be Collected. 'CV' Vendor Attribute Not Found", you must increase the Delay Collection at

Startup (sec) value in the collector's configuration.

For more information, refer to the following topic:

OPC Alarm and Event Collector.

88

Getting Started with Historian

Viewing Historian Values and Time Stamps in an iFIX Chart

When viewing an iFIX chart, set the interval time to a fine granularity to ensure that you will see Historian values and Time Stamps when you zoom in on the chart.

Importing the Historian Toolbar into iFIX

You must import the Historian toolbar into the iFIX WorkSpace after you have successfully installed Historian.

To import the toolbar:

1. Open the iFIX WorkSpace.

2. Select Toolbars from the WorkSpace menu. The Toolbars dialog box appears.

3. Select WorkSpace from the Owners list.

4. Click the Customize button. The Customize Toolbars dialog box appears.

5. Click the Import button. The Import Toolbars dialog box appears.

6. Select Historian from the Toolbars list.

7. Click the Import button to import the Historian Toolbar.

8. Click the Close button. The Customize Toolbars dialog box closes and the Historian Toolbar appears in the iFIX WorkSpace.

NOTE: The Configure Historian Servers toolbar in the WorkSpace specifies the location of historical data retrieval for the WorkSpace, not the location of the historical data storage. You can view/retrieve data stored on these listed servers while you select a pen for a chart display. The Configure Historian Servers dialog also determines where HDA programs and historical ODBC retrieve data from, which is always the default server.

Using the Toolbar Buttons

Use the Change Historian button (left-most button on the toolbar) to switch to Historian mode to browse tags and retrieve data from your Historian Server.

Formatting OPC Tags Containing Special Characters

After selecting an OPC tag in the Expression Builder, you must add single quotes to the pen list in order to handle special characters.

89

Proficy Historian Getting Started Guide

For example:

Hist.node1.Data Point.Int2

`Hist.node1.'Data Point.Int2'

If a single quote (`) or a backslash (\) is a literal part of the addressing string syntax (e.g.

HIST.NODE1.'MIXER'LINE.INT2), it must be preceded by a backslash (\) in order for the character to be passed to the server as part of the address (HIST.NODE1.\'MIXER\'LINE.INT2).

Filtering Tags Using THISNODE with Expression Builder

If you configure an iFIX node to use Local Node Alias and then use for example MIXER as the node name, you can use a filter such as M* to return a list of all tags that start with M including THISNODE. If you use T* as a filter, no tags will be returned, because THISNODE is an alias, not a real node name.

The iFIX Data Collector

Several components of Historian, such as the iFIX Data Collector, work with iFIX. The iFIX Data Collector uses the Easy Data Access (EDA) protocol to retrieve data from a running iFIX system.

The iFIX Install program automatically provides an iFIX node name to the iFIX Data Collector. The default name is iFIXnodename_iFIX. If you browse tags, the Data Collector retrieves every tag with a node name that matches the one you are browsing. Refer to the Historian Data Collector manual for more information on Data

Collector tag configuration.

NOTE: You can install only one iFIX Data Collector per computer.

The preferred way to start an iFIX Collector is to add the collector to the iFIX System Configuration Utility

(SCU) list. The collector then starts automatically whenever you start iFIX.

To add the collector to the SCU list, open the Task Configuration dialog box in iFIX, enter "ihFixCollector.exe" in the Filename field and "runasdos" in the Command Line field, and click the Add button.

IMPORTANT: Stop the iFIX collector before attempting to modify selected iFIX or FIX database blocks and fields you want to be made available in a browse. You can access the blocks and fields from the Configuration tab of the Collector Maintenance screen.

90

Getting Started with Historian

Historian and iFIX Chart Objects

The iFIX chart object plots the last recorded value for pens using Historian tags if the data for those tags comes in from a data collector and the collector loses its connection to the data archiver.

Suppose you configure an iFIX chart object to auto-update the historical data. If the data collector loses its connection to the data archiver, the iFIX chart object flatlines at the last recorded value. When the connection between the collector and archiver is reestablished, the chart then shows the correct data for the period in which the collector was not available.

Optionally, you can use a heartbeat to determine when the iFIX Data Collector stops sending data and restart the collector. For more information, refer to the Example: Restarting the iFIX Collector Using a Heartbeat section in chapter 6 of the Historian Data Collectors guide.

Browsing iFIX Tags On Networked iFIX Nodes

It is recommended that you install an iFIX Collector on each node you want to collect data from. You can choose, however, to use the iFIX networking structure to bring tags into your iFIX Collector from multiple iFIX nodes or systems.

To select multiple nodes to browse from modify the Nodes to Browse field in the Configuration Tab of the

Collector Maintenance screen. This field displays the mask used to select tags when performing a browse of the collector node. The default is the iFIX SCADA or VIEW (iClient) node name that you installed the collector on.

If you want to browse for tags on other iFIX nodes via FIX networking, you can enter the other node name(s) here, separated by commas with no spaces. You must have the iFIX system configured for networking.

For more information, refer to the iFIX Electronic Books on FIX networking.

Creating Historian Charts using Mixed Pens

Historian allows you to put both OPC data source and FIX Tag type pens into your iFIX charts; Classic

Historian only allows you to use Fix Tag pens. Note that if you create a mixed pen chart in iFIX Historian

Mode and attempt to open the chart in Classic Historian mode, you may not be able to view either pen.

Using the iFIX Expression Editor to search tags

Since iFIX tags have a NODE.TAG.FIELD format, you must enter separate node and tag filters when you use the Expression Editor to search for tags. This is important when you search for non-iFIX tags, such as those generated by a Simulation Collector. For example, if the simulation tags have the format T20.Simulation

91

Proficy Historian Getting Started Guide

00001, T20.Simulation00002, etc., which is different from the iFIX format, use a node filter of * and a tag filter of t2* to return all Simulation tags. An iFIX tag with the name T2.Ramp.F_CV would not be returned in that example because the Tag Name (Ramp) does not contain T2. T2 is the node name.

Searching for Calculation or Server-to-Server tags in the iFIX Expression Editor

You cannot use the Calculation or Server-to-Server Collectors as a search filter in the iFIX Expression Builder.

The Calculation or Server-to-Server Collectors do not appear in the Collector Type drop-down list in the iFIX

Expression Builder as an option for filtering.

Using the iFIX Integration Toolkit

If you are using the iFIX Integration Toolkit (HDA) with Historian, you must ensure that the HTRDATA directory path location listed in the SCU contains a folder for each node name and a single file with a valid

Classic Historian Archive name (for example, "00090300.H24"). If this structure is not in place, all

"HdaEnumNodes" calls will fail to return the list of remote nodes. The file does not need to be created by HTC and does not need to contain any historical data. You can create the files using Notepad by saving an empty file as "00090300.H24" including the quotation marks to <Drive:\htrdata\><Remotenodename> where the path matches the HTR data path in the SCU.

GE Intelligent Platforms recommends that all new custom historical data applications be built using the

Historian SDK.

Uninstalling Historian if iFIX v2.6 is installed

If iFIX v2.6 is installed, when you uninstall Historian, you should select No if prompted to remove the shared file named SPR32X30.OCX, the Farpoint Spreadsheet v3.0 (a third-party ActiveX control).

If the install removes the SPR32X30.OCX file, the iFIX WorkSpace reports a VBA compile error the next time you open the iFIX WorkSpace.

If you receive the compile error when you open the iFIX WorkSpace, run the following command from the iFIX base path: regsvr32 SPR32X30.OCX

This command re-registers the Farpoint Spreadsheet.

92

Getting Started with Historian

Using v7.x Drivers with Historian

Consult the following topics for using the iFIX v7.x drivers with Historian

Using Autocreate

Using the Latched Data feature

Running iFIX 7.x Drivers as OPC Servers

Running iFIX 7.x Drivers as a service with Automatic Startup

Using Autocreate

iFIX 7.X drivers have an AutoCreate feature that automatically generates datablocks if an iFIX Database or an

OPC Collector requests them. If you have enabled AutoCreate in an Intellution 7.X driver that you are using with Historian, any datablock deleted from a group will be recreated by the next collector request. To stop the recreation, disable AutoCreate for the driver. You cannot specify only iFIX AutoCreate.

Using the Latched Data feature

iFIX 7.X drivers running as OPC Servers have a latched data feature. If you select this feature, the driver continues to display the last known good value, even when a connection to the process hardware is broken. The

Historian OPC Collector considers the latched values as bad data and does not collect the values.

Running iFIX 7.x Drivers as OPC Servers

Current versions of iFIX 7.X drivers can run as OPC Servers. If you are running 7.X drivers as OPC Servers, you must either run the 7.X driver on a computer with iFIX installed or install the new hardware key.

Running iFIX 7.x Drivers as a service with Automatic Startup

The following procedure details the steps needed to set up your iFIX 7.X driver to run as a service with automatic startup. The procedure describes a specific ABR driver setup which requires RSLinx; however, you can also use the steps to configure your other 7.X drivers by substituting the driver name and other specific driver information. If your driver requires a third party software, such as RSLinx, ensure that it is configured properly as a service before moving on to step 2.

To set a collector to run as a service with the ABR driver:

1. Install and configure Rockwell Software's RSLinx.

93

Proficy Historian Getting Started Guide

2. Install an ABR OPC Server.

3. Create an ABR Configuration, save it, and configure it for auto start.

4. Install and configure your OPC Collector: a. Install an OPC collector. The Historian install prompts you for a Prog ID and a name. b. Enter Intellution.ABROPC. c. Choose not to restart your system.

5. Configure DCOM defaults.

NOTE: You should only need to configure DCOM on your Windows computer once.

a. Select Run from the Start menu and enter DCOMCNFG. The Distributed COM Configuration

Properties dialog box appears. b. Select the Default Security tab. c. Click the Edit Default button in the Default Access Permissions section. d. Click the Add button to add System and Interactive Groups (if not present). e. Click OK to return to the Distributed COM Configuration Properties dialog box. f. Click the Edit the Default button in the Default Launch Permissions section. g. Click the Add button to add System and Interactive Groups (if not present). h. Click OK to return to the Distributed COM Configuration Properties dialog box. i. Click Edit the Default button in the Default Configuration Permissions section. j. Click the Add button to add System and Interactive Groups (if not present). k. Click Apply and OK to close the DCOM configuration utility.

6. Register Intellution OPC Server to run as a service: a. Ensure that the Power Tool and all clients are shut down. b. At the run prompt, enter the following:

ABRdrv REGSERVICE

Note that this text is case sensitive. a. Verify that the ABR OPC Server appears in the Services dialog box. If it does not, you may have entered it incorrectly. Ensure that all client applications to the driver, including the

Power Tool, are closed and the Services Dialog is closed. If all client applications are closed, try entering the string again.

7. Start the Server manually through the Services Dialog in the Control Panel.

94

Getting Started with Historian

8. Start the Collector manually through the Control Panel.

9. Log into the Historian Administrator and add all of the tags from the collector.

10. Open the Run prompt from the Start Menu.

11. Enter Regedt32 in the Open field and set the following dependencies:

Set the Dependency of the iHOPCCollector on the OPCServer: a. Locate the iHOPCCollector folder. This folder is typically located in the

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iHOPCCollector path. b. Add a value to the iHOPCCollector registry key:

I. Select Add a Value from the Edit menu.

II. Enter the following exactly in the Value field:

DependOnService c.

III.

IV.

V.

VI.

Select REG_MULTI_SZ as the data type.

Click OK. A dialog box appears prompting you to enter the value.

Enter ABRdrv.

Click OK.

Set Dependency of OPC server on its 3rd party API:

NOTE: This dependency only applies to the ABR and other drivers which require a 3rd party API.

For all other 7.X drivers, only set the iHOPCCollector dependency.

I. Locate the ABRdrv folder. This folder is typically located in the

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ABRdrv path.

II. Add RSLinx to DependOnService:REG_MULTI_SZ value.

12. Open Services in the Control Panel.

13. Select and set the ABRdrv and iHOPCCollector Startup to automatic.

14. Configure RSLINX to run as a Service: a. b.

Select Options from the View menu.

Select the Service Tab. c. Select the Run as a Service check box.

15. Restart your computer.

16. Verify that all services started, and that data is being collected.

95

Proficy Historian Getting Started Guide

Troubleshooting iFIX and Historian

Consult the following topics for troubleshooting iFIX and Historian.

Running iFIX as a service with Workspace listed in the SCU Task List iFIX Workspace delay when remote session is lost

Starting iFIX when a remote Historian session is unavailable

Accessing Mission Control when a remote Historian session is lost

Using the iFIX V2.6 chart with Historian domain security enabled

Accessing tags in the iFIX chart after setting OPC Collector to "Made After Restart"

Collecting data in an iFIX chart with Time Assigned By Source

Running iFIX as a service with Workspace listed in the SCU Task List

Prior to iFIX 5.1, if you have configured iFIX to run as a service, you should not have WORKSPACE.EXE listed as a configured task in the Task Configuration dialog box of the SCU. If WORKSPACE.EXE is listed as a configured task, it may lead to unpredictable results. For example, if you are also running Historian, no servers will appear in the Server Name field of the Configure the Historian Server dialog box and you will not be able to browse Historian tags in the iFIX Expression Editor.

To rectify this, remove WORKSPACE.EXE from the list of configured tasks in the SCU.

iFIX Workspace delay when remote session is lost

If the connection between iFIX and a remote Historian session is lost, you may experience a 90 second delay in the iFIX Workspace Configuration environment, chart, or Expression Builder when accessing a pen associated with that Historian session.

In the Run Time Environment, all pens in a chart disappear for 90 seconds when the session to a remote

Historian session is lost, even if they are associated with a local Historian server.

Starting iFIX when a remote Historian session is unavailable

If you are using Historian with iFIX, the iFIX Workspace attempts to connect to the Historian Server when it starts up. If a remote Historian server is unavailable, it may take one minute or longer for iFIX Workspace to display for each unavailable server.

96

Getting Started with Historian

Accessing Mission Control when a remote Historian session is lost

If a remote Historian session is lost while you are accessing `the HTC tab of Mission Control in the iFIX

Workspace, the H tab may blank out for a minute or longer.

Using the iFIX V2.6 chart with Historian domain security enabled

If you have enabled Historian Domain Security in the Historian Administrator, you will need to download the latest iFIX v2.6 SIM to use the iFIX Chart. For more information on iFIX SIMs, refer to http://support.geip.com/downloads/sims/ or contact your local sales representative.

Accessing tags in the iFIX chart after setting OPC Collector to "Made After

Restart"

If you add tags in the Historian Administrator to a Server from an OPC Collector that has Configuration

Changes set to Made After Collector Restart, you will be able to see those tags in the iFIX Expression Builder.

You can add them to a chart, for example, but they have no collected data until you manually stop and restart the OPC Collector.

Collecting data in an iFIX chart with Time Assigned By Source

If you are retrieving data in an iFIX Chart from an Historian Server, have set the Time Assigned by field to

Source, and have collectors running behind the Server time, the chart will display a flatline up to the current time of the local machine.

NOTE: You must set Time Assigned by field to Source if you have unsolicited tags getting data from an OPC

Collector.

Synchronizing the time on iFIX SCADA Servers and View Clients

To ensure that acknowledgements are not lost or attributed to the wrong alarm, synchronize the clocks on

SCADA servers and iFIX View Client machines. If the clocks are not synchronized, alarms generated on the

SCADA nodes and acknowledged on the iFIX View Client nodes could have significantly different timestamps.

You can synchronize the clocks using the NET TIME command. Refer to the Windows Help system for more information.

97

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents