OSIsoft PI Historian and AF Connector

OSIsoft PI System Historian & OSIsoft AF servers

On This Page:

Overview

The OSIsoft PI System protocol enables seamless integration with your solution, allowing it to function as a historian provider without requiring additional historian configuration. When a tag is mapped to a PI point, the system automatically retrieves data directly from the PI Server for use in trend charts, scripts, or any display requiring historical information.

Your solution can simultaneously use both the built-in historian and the PI System. When historical data is requested, the system first checks the built-in historian module. If the requested information is unavailable, it automatically queries the PI Server.

Channel Configuration

Protocol Options

When writing to AF:

• Default: default configuration, does not includes the Tag's timestamp when writing to the PI Server 
• Write to PI Point: Includes the Tag's timestamp when writing to the PI Server

Node Configuration

Primary Station 

Station syntax:  <IP >;<ServerType>;<PI Server Name>;<AF DataBase>

Where :

•  <IP> = IP address of the PI Server in the network.
• <ServerType> = The type of the Server you wish to connect to. Could be either a PI Server ou a AF Server.
• <PI Server Name> = The connected server`.
• <AF DataBase> = Name of the AF DataBase being connected to (usable only if the ServerType configuration was set to AF Server).

Station Example

PrimaryStation =  127.0.0.1;AF;WIN-PSMAPEDPEJR;Configuration;

Points Configuration

Address

To configure it, go to Devices/Points and click on the Address column to edit.

Point syntax:  <Address>

<Address> indicates the Tag's address inside the PI Server which is being accessed by the PI Point. 
After creating the communication point, you can use either the "Browse AF tree" or the "Browse PI tags" to open the PI points/AF search dialogs and directly select the desired tag inside the PI server to map to the Communication Point, as can be seen here: 

After setting the communication point up, you can click on the Verify button to check what value is being read in the specified address. 

Diagnostic Tools

Diagnostics tools refer to the Property Watch, Trace Window, and Module Information. These tools identify communication blocks and address errors, allow property access to pinpoint error causes, and display system messages for device management and troubleshooting, offering a comprehensive approach to device management and troubleshooting for Solutions on the software platform.

Module Information

This tool provides insights into module operations and communication channels, offering information about virtual reading groups, error codes, and communication events. It helps users identify communication blocks and effectively address errors in industrial automation systems.

Property Watch

This tool enables users to access, read, and write tags and internal properties of the system. It assists in identifying the root cause of errors through negative error codes, allowing for real-time adjustments and optimizations to the system configuration.

Trace Window

This tool displays system messages in a data grid interface, providing information about the status of reads, writes, and communication frames. It is particularly useful for various PLCs and communication protocols, as it presents invalid addresses in the configuration, assisting in device management and troubleshooting.

Driver Revision History

In this section: