| Easy Heading Macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|
The GEProficy Protocol Driver connects the software platform with the GE Proficy Historian, enabling data exchange. The GE Proficy Historian collects, stores, distributes, and retrieves industrial time series and A&E data. The GEProficy Protocol Driver allows for real-time data capture, ensures secure storage, and supports retrieval, enhancing data accessibility for analysis.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Summary
Communication Driver Information | |
|---|---|
Driver name | GE Proficy Historian Connector |
Assembly Name | T.ProtocolDriver.GEProficy |
Assembly Version | 1.0.0.0 |
Available for Linux | True |
Database supported | Proficy Historian via GE API |
Manufacturer | GE |
Interface | Custom |
Protocol | TCP/IP |
PC Requirements | Ethernet port |
Configuration
All initial configurations for devices in the solutions on the software platform encompass the following workflow:
Defining a Channel using a target communication Protocol creates the base instance for linking a Node. Learn more at Devices - Channels.
Defining the Node linked to the created Channel. Learn more at Devices - Nodes.
Defining the Point that you would like to monitor. Learn more at Devices - Points.
Protocols define communication rules between the platform and devices. Channels define global parameters for using a communication protocol. Nodes represent physical field devices (like a PLC) or database with a unique field address (PrimaryStation). Points represent tags within a devicefrom database. Additionally, AccessType defines how the device interacts with the platform (Read and/or Write). Learn more atDevices - AccessType.
Channels
Protocol Options
Protocol options are not used in this driver. The remaining channel configurations are the same as in the reference guide.
Nodes
Station Configuration
Server Name: Historian sever name.
User Name: User name to access the Historian server.
User Password: User password to access the Historian server.
Points
AccessTypesAddress
The syntax for the communication points are:
TagName: Tag Name in Database.
Note1: Use the Verify button to check if it is a valid name and get the current value and quality.
Note2: Select the tag name in Database using the Browse button.
Driver Revision History
GE Proficy Driver Revision History | |
|---|---|
Version | Notes |
1.0.0.0 | Initial release on new documentation standards |
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|