CoreM Server data exchange

On This Page:

Overview

CoreM Connector retrieves data from the GE Proficy Historian Database, displaying a multi-level structure composed of Plant, Area, Line, Equipment, and Variables. The configuration involves defining a Channel using a target communication Protocol, linking a Node to this Channel, and defining Points to monitor.

Configuration

All initial configurations for devices in the solutions on the software platform encompass the following workflow:

1. Defining a Channel using a target communication Protocol creates the base instance for linking a Node. Learn more at Devices - Channels.

2. Defining the Node linked to the created Channel. Learn more at Devices - Nodes.

3. Defining the Point that you would like to monitor. Learn more at Devices - Points.

Protocols define communication rules between the platform and devices or databases. Channels define global parameters for using a communication protocol. Nodes represent each Database with a unique field address (PrimaryStation). Points represent tags within a device. Additionally, AccessType defines how the device interacts with the platform (Read and/or Write). Learn more at Devices - 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: Database server name 
Database Name: Model database name 
User Name: User name to access the Model database. 
User Password: User password to access the Model database. 
Trusted Connection:  Enable the Integrated Security with the database. 

Note: Use the Test button to check the connection with the Server and Database. 

Points

Address

The syntax for the communication points are:

Plant: Select the desired plant from the database.

Area: Select the desired area from the plant.

Line: Select the desired line from the area.

Equipment: Select the desired equipment from the line.

Variable: Select the desired variable from the equipment.

Driver Revision History

In this section: