IMD SolutionComputing LibraryShop main store

Troubleshooting

Read Proficy Historian OPC-HDA tags into Ignition

Edge computing and IIoT Published 7 min read

Short answer

Create the Proficy historical connection through the OPC COM module's documented OPC-HDA workflow, not the new OPC Server connection dialog. Charts get their data from interval reads; values usable as Designer tags need a runScript bridge into a shared script built on system.opchda.readRaw. Enabling tag history on bridged tags stores new values only — the existing Proficy archive is not migrated.

On this page
  1. Why is OPC-HDA missing from the new OPC Server connection dialog?
  2. How do you point the historical provider at the Proficy server?
  3. Why does Easy Chart browse the tag but show no samples?
  4. How do you turn an OPC-HDA item into a usable Designer tag?
  5. Does enabling tag history copy the Proficy archive into SQL Server?
  6. Is OPC-HDA the best route from Proficy into Ignition?
  7. Questions asked

Ignition 7.9.12 does read GE Proficy Historian history — through the OPC COM module's OPC-HDA workflow, which lives under Tags, History in the gateway configuration section, not in the dialog that creates a new OPC Server connection. The historical provider you build there serves interval reads to charts and scripts; it never becomes a live Designer tag by itself. Three outcomes come out of that one connection: chart Proficy history directly, bridge chosen values into expression tags through a runScript call into a shared script built on system.opchda.readRaw, and switch on tag history for the bridged tags when other systems must store or consume them. The identifiers used below come from one 7.9.12 deployment and show the shape of the thing; your ProgID, provider name and item paths come from your own installation.

Why is OPC-HDA missing from the new OPC Server connection dialog? #

Because that dialog only creates live server connections: an OPC-HDA connection is a separate, documented workflow of the OPC COM module, reached under Tags, History in the gateway configuration section — install the module, then create the historical provider there.

The base platform ships an OPC UA client that needs no module, so a connection dialog full of live servers with no HDA anywhere reads as a missing feature. It is a split in where things live, not a gap. The OPC COM module adds OPC DA and OPC-HDA for local and remote COM servers, on 32-bit and 64-bit gateways, and its documentation carries the OPC-HDA connection procedure under its own heading.

  1. Confirm the OPC COM module is installed and enabled on the gateway.
  2. Open the gateway configuration section and go to Tags, History.
  3. Use the module's documented create action for the OPC-HDA connection there.
  4. Reserve the new OPC Server connection dialog for live DA and UA servers.

Decision: fix the module and the workflow before weighing any upgrade; the ordinary dialog still creates only live connections.

How do you point the historical provider at the Proficy server? #

Select the registered server by its COM ProgID — Proficy.Historian.HDA in the deployment described here — and give the resulting historical provider a name; charts and scripts then address that provider name plus an exact browsed item path.

The three identifiers do different jobs, and swapping one for another is the most common configuration error:

Identifier Value in one 7.9.12 deployment Job
COM ProgID Proficy.Historian.HDA Selects the registered Proficy historical COM server
Historical provider name Proficy The name charts and scripts call
OPC-HDA item path Compact_PME.fm2_DelayFlow One archived item inside that provider

Remote operation rides Windows COM/DCOM, so a browse failure is about network reachability, the gateway service's Windows identity, COM activation and access permissions on the historian host — the same class of fault as troubleshooting an OPC-HDA browsing error 80040005 against a PI server. A provider that reports Running and browses items has proven that whole chain; treat everything after it as a read problem, not a connection problem.

Why does Easy Chart browse the tag but show no samples? #

Browsing asks which archived items exist; a chart plots the samples the server returns for an interval, and OPC-HDA returns those only through interval reads — so prove samples with a raw read before touching chart settings.

OPC-HDA is the OPC Historical Data Access specification, the COM-era companion to OPC Data Access. In its own terms: the client names an item and a start and end time, and the server answers with a timestamp, value and quality for each archived sample. Nothing in it subscribes to a current value the way a DA or UA client subscribes. That is why a browse that succeeds while the chart stays empty has exactly three usual causes: the interval holds no samples, the chart is not actually pointed at the historical provider's item, or the chart's time basis does not match the archive's timestamps.

  1. Pick an item with a known recorded change in Proficy.
  2. Set the chart interval to include that change, and compare the chart's time basis, including time zone, with the archive timestamps.
  3. Confirm the chart references the historical provider and the exact browsed path, not a same-named Designer tag.
  4. Call system.opchda.readRaw for the same provider, path and interval, and read the returned sample count, timestamps, values and quality.
  5. Branch on that result: samples returned means a chart configuration fault; no samples means the interval or the archive collection; an error means the gateway log and the server's own diagnostics.

The provider-and-interval discipline is the same one that settles faults when you query tag history from a remote tag provider, so the checklist transfers. Decide on the raw read, never on the empty chart.

How do you turn an OPC-HDA item into a usable Designer tag? #

Build one expression tag per value whose runScript call hands a shared script the provider name and the item path; a working deployment used runScript('shared.getOpcHdaValue',0,'Proficy','Compact_PME.fm2_DelayFlow'), with the shared function returning the first sample of the last minute.

The expression is one line, changed per tag only in the item path argument:

runScript('shared.getOpcHdaValue',0,'Proficy','Compact_PME.fm2_DelayFlow')

The shared function's contract, as deployed:

  • call system.opchda.readRaw on the supplied provider and path over a time window,
  • return the value of the first sample that comes back,
  • note that the 0 in the expression is the polling argument: 0 runs the function when the expression evaluates, not on a timer.

Worked example, illustrative numbers: assume the archive collects this item every 10 s — the real figure comes from the Proficy archive configuration. The deployed 60 s window spans 60 / 10 = 6 samples, and returning the first one leaves a value up to about 60 s old in the tag even when the archive is current. The window only has to exceed the collection interval to guarantee at least one sample: over a 10 s collection, a 15 s window still guarantees one, because the longest possible gap is 10 s, and it caps staleness near 15 s. Keep the 60 s window for slow indications and audit-style values; drop to just above the collection interval for anything driving a fast display.

One safety note: a bridged tag's freshness is bounded by the read window, not by the process, so never feed protection or interlock logic from it.

Decision: bridge only the values other controls actually consume, and leave everything else as a chart query.

Does enabling tag history copy the Proficy archive into SQL Server? #

No: tag history on a bridged expression tag records the values the bridge produces from the moment it runs, timestamped on the Ignition side; the existing Proficy archive stays in Proficy and is not migrated by this setting.

Once the bridged tags exist, the store-and-query mechanics are the same path used when logging PLC values from an OPC server into SQL Server: tag history writes to the gateway's configured database — SQL Server in that deployment. Size the store before switching it on. Illustrative numbers: one stored value every 30 s is 86,400 / 30 = 2,880 rows per tag per day, and 50 bridged tags write 2,880 × 50 = 144,000 rows per day. Retention and purge settings follow from that rate.

  • View Proficy history: leave it in Proficy and chart the historical provider; copy nothing.
  • Feed other controls: bridge the tags and leave history off.
  • Feed other systems a second copy: enable history on the bridged tags and size retention against the row rate.

Before standing up a second store at all, settle whether you need a historian or just an OPC tag server.

Is OPC-HDA the best route from Proficy into Ignition? #

For charting existing Proficy history, yes: the OPC-HDA historical provider is the documented route and needs no data copied. For live values and new history, a live OPC DA or UA interface on the historian side is the better route when your installation exposes one.

A live route exists only if the historian side actually offers it — read the installed Proficy configuration for exposed interfaces, because the HDA interface in this deployment was COM-based and the module was built for exactly that. The bridge is not a migrator either: it re-reads the current window, so moving the full archive is a separate export task on the Proficy side with its own validation.

Decisions, one per case:

  • Existing archive to screens: historical provider and Easy Chart, no copies.
  • Live values to controls: a live DA or UA connection if one exists; otherwise the bridge with the shortest window that still guarantees a sample.
  • A permanent second copy: bridged tags with history on and retention sized by the row rate — or a proper archive export when fidelity matters.

Questions asked

How do you find the COM ProgID for our historian?

Open a general OPC client on the historian host, browse the registered OPC servers, and use the ProgID that clearly belongs to the Proficy historical server — Proficy.Historian.HDA in the deployment described here. The ProgID names a registered COM server class, so it only appears where the server software is actually installed.

How often should the bridge expression refresh?

Replace the 0 polling argument with an interval in milliseconds, for example 5000 for a five-second refresh. At 5000 ms one tag runs 3,600,000 / 5000 = 720 reads per hour, so 50 tags issue 36,000. Match the rate to what the display actually needs rather than polling flat out.

Can the built-in OPC UA client replace the OPC COM module here?

Only if the historian side exposes an OPC UA endpoint. The base platform's OPC UA client needs no module, but it speaks UA, not the COM-based OPC-HDA interface this historian presented, so that deployment needs the module. Check the installed Proficy configuration for a UA endpoint before deciding.

What is lost when historizing bridged tags instead of migrating the archive?

Original sample timestamps, the server's per-sample quality flags, and the archive's own spacing. The Ignition store holds the values the bridge produced, stamped when the tag executed. For a faithful copy, run a proper export from the Proficy side and validate row counts and timestamps against known events.

Can scripts browse the HDA server as well as read it?

Yes: the same scripting scope offers system.opchda.browse for enumerating items, which is handy for generating tag lists. Browsing still returns items, never samples — only read functions such as system.opchda.readRaw return values, and only over an interval you supply.

Keep reading

  • Explainer

    Do you need a historian or just an OPC tag server?

    No. An OPC tag server (OPC DA) supplies the current value, quality and timestamp of each item and stores nothing, so monthly figures need a historian or a SQL logger collecting from that same server. Keep a reporting client like ActiveFactory only if you also run the historian it expects.

    Edge computing and IIoT

  • Comparison

    Move DeltaV Continuous Historian data into a PI system

    When PI points exist, collect DeltaV live values with OPC DA and recover history with OPC HDA; when points and AF structure are missing, let the DeltaV Smart Connector create them from EntHist.xml. Add PI-to-PI only for a second office-LAN server. Prove buffering, service identity and archive coverage by test before the bulk load.

    Edge computing and IIoT

  • How-to

    Collecting Modbus turbine data into a plant historian

    A Modbus port on an older turbine control panel can feed a plant historian, but it cannot deliver millisecond updates and it carries no controller time tags. Prove the physical link, decode one register against the operator display, choose the collection path, then set the poll interval from measured transaction time — the worked example here puts one 20-register read at about 69 ms of wire time at 9600 baud, so a multi-block sweep lands far above 100 ms.

    Edge computing and IIoT