Pi interface for Siemens Spectrum Power tg (Linux)


Notes for bufserv on Linux



Download 0.55 Mb.
Page14/18
Date29.01.2017
Size0.55 Mb.
1   ...   10   11   12   13   14   15   16   17   18

Notes for bufserv on Linux

apiverify Warning

When buffering is enabled, there will be a parent bufserv process running and another bufserv process for each of the PI Servers configured for buffering. Therefore, when buffering is configured for 2 PI servers, there should be 3 instances of the bufserv process running. When the apiverify is used to check the running processes, ignore "WARNING: multiple instances of bufserv are running".

Sample piclient.ini file


The follow are typical samples of the piclient.ini files.

The first sample has buffering enabled for a single PI server named PISERVER. The buffer sizes for both buffer 1 and buffer 2 are set to 1MB each (1048576 bytes). The delay between blocks of events is 100 milliseconds and each block can be up to 5000 events.



[PISERVER]
PIHOMENODE=PISERVER
DSTMISMATCH=3600


[TCP/IP]
PORT=5450


[APIBUFFER]
BUFFERING=1
BUF1SIZE=1048576
BUF2SIZE=1048576
SENDRATE=100
MAXTRANSFEROBJS=5000


[BUFFEREDSERVERLIST]
BUFSERV1=PISERVER
#BUFSERV2=srv2


[REPLICATEDSERVERLIST]
#REPSERV1=srv1
#REPSERV2=srv2

The second sample has a similar configuration for the buffering, but the events are being sent to 2 PI servers that are members of a collective, so the events sent to one must be replaced to the other.



[PISERVER]
PIHOMENODE=PISERVER_PRI
DSTMISMATCH=3600


[TCP/IP]
PORT=5450


[APIBUFFER]
BUFFERING=1
BUF1SIZE=1048576
BUF2SIZE=1048576
SENDRATE=100
MAXTRANSFEROBJS=5000


[BUFFEREDSERVERLIST]
BUFSERV1=PISERVER_PRI
BUFSERV2=PISERVER_SEC


[REPLICATEDSERVERLIST]
REPSERV1=PISERVER_PRI
REPSERV2=PISERVER_SEC


  1. Interface Diagnostics Configuration


The PI Point Configuration chapter provides information on building PI points for collecting data from the device. This chapter describes the configuration of points related to interface diagnostics.

Interface Specific Performance Points


To monitor the status and performance of the interface as it processes the files, the interface supports a number of performance PI points that are specific to this interface. Because the interface is able to process two different types of input file, there are two sets of performance points. One set of points for the measurement data and another for the alarm messages.

To indicate that a PI point is an interface-specific performance point, Location2 must be set to -1. To identify the performance value to be stored in the point, the interface checks the ExDesc attribute for a specific keyword. The following is a list of the keywords, the expected PI PointType and a description of the value.



ExDesc Keyword

PointType

Description

DATA_LATEST_TIMESTAMP

Float64

Timestamp of the latest event found in the data file.

DATA_EVENTS_FOUND

Int32

Total number of events found in the data file.

DATA_EVENTS_SENT

Int32

Total number of events sent to the PI system from the data file.

DATA_FILE_STATUS

Digital

Status to indicate whether the data file was processed cleanly or whether errors were found. See the section File Status State Set for the digital set definition.

DATA_TIME_TAKEN

Float32

Number of milliseconds the interface took to process the data file.

ALARM_LATEST_TIMESTAMP

Float64

Timestamp of the latest event found in the alarm file.

ALARM_EVENTS_FOUND

Int32

Total number of events found in the alarm file.

ALARM_EVENTS_SENT

Int32

Total number of events sent to the PI system from the alarm file.

ALARM_FILE_STATUS

Digital

Status to indicate whether the alarm file was processed cleanly or whether errors were found. See the section File Status State Set for the digital set definition.

ALARM_TIME_TAKEN

Float32

Number of milliseconds the interface took to process the alarm file.

If the PI point does not have the same PointType as those listed, the PI point will be rejected by the interface.

A set of sample interface-specific performance points are included with the interface install kit.



Note: The xxxx_LATEST_TIMESTAMP performance points are important when the interface is running in a redundant configuration, as it will help to reduce the overlapping data when the failover occurs.

Sample Interface Specific Performance Points


The file SIPowerTG_Interface_Health_Tags.csv including in the install kit contains a set of typical Interface Specific Health Points that can be used to monitor the performance of the interface.


Download 0.55 Mb.

Share with your friends:
1   ...   10   11   12   13   14   15   16   17   18




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

    Main page