Appendix a. error and informational messages, Message logs, Messages – Rockwell Automation FactoryTalk Historian SE 3.0 H2H Interface User Guide User Manual

Page 143: Interface startup messages, Appendix a, Error and informational messages, Appendix a: error and informational, Appendix a: error and, Informational messages, Messages interface startup messages

Advertising
background image

FactoryTalk Historian To Historian Interface User Guide

137

Appendix A.

Error and Informational Messages

A string

NameID

is pre-pended to error messages written to the message log.

Name

is a non-

configurable identifier that is no longer than 9 characters.

ID

is a configurable identifier that

is no longer than 9 characters and is specified using the

/id

parameter on the startup

command-line.

Message Logs

The location of the message log depends upon the platform on which the interface is running.
See the UniInt Interface User Manual for more information.

Messages are written to

PIHOME\dat\pipc.log

at the following times

.

When the interface starts many informational messages are written to the log. These

include the version of the interface, the version of UniInt, the command-line
parameters used, and the number of points.

As the interface retrieves points, messages are sent to the log if there are any

problems with the configuration of the points.

If the

/dbUniInt

is used on the command-line, then various informational messages

are written to the log file.

Messages

Interface Startup Messages

When the interface is started, the log file will contain informational messages that describe
the settings that will be used from the startup script and the

PItoPI.ini

file. The interface

will then print a message stating the receiving Historian Server and a message for each source
Historian Server. The message for each source Historian Server also states the time offset
between source and receiving Historian Server along with time zone differences. Note that
the

PItoPI.ini

can be used to configure a different source server for each scan class. In

addition each source server (and therefore scan class) can have different history recovery
parameters. Finally the

PItoPI.ini

can be used to specify which scan class signs up for

exceptions (default is scan class 1 gets exception data unless

/hronly

is specified in

PItoPI.bat

). After printing a message specifying the receiving and source Historian

Servers it prints a message for each scan class stating if it will collect archive or exception
data, the source Historian Server for that scan class and the history recovery parameters.

Advertising