Pi interface for Siemens Spectrum Power tg (Linux)



Download 0.55 Mb.
Page4/18
Date29.01.2017
Size0.55 Mb.
1   2   3   4   5   6   7   8   9   ...   18

Installation Checklist


If you are familiar with running PI data collection interface programs, this checklist helps you get the interface running. If you are not familiar with PI interfaces, return to this section after reading the rest of the manual in detail.

This checklist summarizes the steps for installing this interface. You need not perform a given task if you have already done so as part of the installation of another interface. For example, you only have to configure one instance of Buffering for every interface node regardless of how many interfaces run on that node.

The Data Collection Steps below are required. Interface Diagnostics and Advanced Interface Features are optional.

Note: The SIPowerTG interface version 1.0.0.0 on Linux is only compatible with PIAPI 1.6.1.11 on Linux. The interface is NOT compatible with later versions of the PIAPI because of the version of the C++ compiler used to build the interface and the PIAPI.

The SIPowerTG interface version 1.0.1.0 or later on Linux is compatible with PIAPI 1.6.4.x or later.


Data Collection Steps


1.Confirm that you can use PI SMT to configure the PI Server. You need not run PI SMT on the same computer on which you run this interface.

2.Edit the PI Server’s Trust Table to allow the interface to write data.

3.Check the interface nodes time zone properties. An improper time zone configuration can cause the PI Server to reject the data that this interface writes.

4.Run the installation kit for this interface on a Windows machine. Copy the extracted SIPowerTG_x.x.x.x_Linux64.tar.gz file and the PIAPI install kit file to the Power TG machine.

5.Extract the contents of the PI API install kit and run the pi.install installation script.

6.Start the PI API processes and use apisnap to verify the connection to the PI server.

7.Extract the interface installation kit into the $PIHOME directory.

8.Replace the sitestart and sitestop scripts in the $PIHOME/bin directory with the scripts included in the interface directory.

9.In the interface directory, use the template startup script to create the startup script for the interface and edit the command-line parameters. Essential startup parameters for this interface are:

Point Source (-PS=x)

Interface ID (-ID=#)

PI Server (-Host=host:port)

Measurement Data File (-DATA=x)

Alarm Message File (-ALARM=x)

Quality Code File (-QUALCODEFILE=x)

Do NOT configure Scan Classes (-F=##:##:##,offset)

10.Use the DumpInputFile and DumpAlarmFile utilities to confirm the format of a sample event data and alarm message files.

11.If you will use digital points, define the appropriate digital state sets. The sample file SIPowerTG_digital_set.csv can be imported with PI SMT to create the file status and default quality digital sets.

12.Check the contents of the data quality definition file (data_qualitities.ini) and ensure that the TG_DATA_QUALITY digital state set matches the priorities defined in the file.

13.Build input tags and, if desired, output tags for this interface. Important point attributes and their purposes are:

Location1 specifies the interface instance ID.

Location2 specifies the point type (performance, value or alarm).

Location3 is not used.

Location4 MUST be zero. (All points are unsolicited)

Location5 specifies whether debug messages will be logs for this point.

ExDesc not used by the interface. Normally set to the Power TG point name.

InstrumentTag specifies the Power TG point number, field and data type for measurement data points or the filter expression for alarm points.

14.Start the interface interactively and confirm its successful connection to the PI Server without buffering.

15.Confirm that the interface collects data successfully.

16.Stop the interface and configure the buffer server application (bufserv).

17.Start the buffering application and the interface. Confirm that the interface works together with the buffering application by either physically removing the connection between the interface node and the PI Server Node or by stopping the PI Server.

18.Replace the default sitestart and sitestop scripts with those included in the install kit so that the interface will start and stop when the pistart and pistop scripts are used.

19.Restart the interface node and confirm that the interface and the buffering application restart.

Interface Diagnostics


  1. Configure the Interface Specific performance points.

  2. Configure UniInt Health Monitoring points

  3. Configure the I/O Rate point.

  4. Install and configure the Interface Status Utility on the PI Server Node.

  5. Configure the Interface Status point.

Advanced Interface Features


  1. Configure the interface for disconnected startup. Refer to the UniInt Interface User Manual for more details on UniInt disconnected startup.



  1. Interface Installation on Linux


The interface is installed on the Power TG station. It is recommended that the PI API Bufserv utility is also run on the Power TG station. Bufserv is a utility program that provides the capability to store and forward events to a PI Server, allowing continuous data collection when the server is down for maintenance, upgrades, backups, and unexpected failures. It is not critical to install Bufserv before the initial installation of the interface. In fact, it is recommended that Bufserv be activated after the interface has been shown to work to ease troubleshooting. Refer to the PI API manual for installation instructions and additional information on Bufserv.

Currently there is no PI Buffer Subsystem for the Linux platform. PI API Buffer Server is the only type of buffering available for the Linux platform.




Download 0.55 Mb.

Share with your friends:
1   2   3   4   5   6   7   8   9   ...   18




The database is protected by copyright ©ininet.org 2020
send message

    Main page