Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide - Manual (Page 11)

UniInt Interface User Manual 5
Standard Parameters
These command-line parameters are used in the every-day running of an interface. This table
does not contain the entire list of parameters supported by UniInt. There are parameters that
are specific to configuring disconnected start-up discussed in the Disconnect Start up section
(page 54) and parameters specific to configuring UniInt Failover discussed in Configuring
UniInt Failover section (page75). None of the parameters are case sensitive. For example,
/ps=ifc is equivalent to /ps=IFC.
Parameter Description
/AppName=Name
Optional
Default = 1st four
characters of the
interface executable
The /AppName=Name controls the name sent to the
Historian Server in order to establish the PI API trust. Prior to
version 4.1 of UniInt, the interface name was used to establish
the PI API trust with the Historian Server. This limited the
Historian
Administrator‟s options when setting up security for
an interface node. There was no way to configure different PI
API trusts for different instances of the interface running on
the same computer. The Historian Administrator is now able to
specify an application name for each instance by using the
/AppName=Name parameter.
The maximum length of the Name is 4 characters. Please
keep in mind when setting up the Trust that the PI API puts an
E at the end of the application name.
The Application Name that is sent to the Historian Server can
be viewed in the Historian Server Message Log immediately
after an interface is started. A message will be written to the
message log stating the connection status for a “process
name”. The “process name” is the application name sent from
the interface.
/dbUniInt=level
Optional
Defualt = 0
The /dbUniInt parameter is used to set a debug level for
debugging UniInt code. level is a 32-bit integer. Setting a
particular bit in level to 1 turns on a particular debug
switch. To turn on every debug switch specify:
/dbUniInt=0xFFFF
level can be specified as either a decimal number or a
hexadecimal number. A 0x must precede hexadecimal
numbers.
The following table lists the sections of code that can provide
debug information and the hexadecimal value that
level
must equal in order for that section to output messages.
Multiple sections can output debug messages simultaneously
by adding the values together. For example, both initiailization
and shutdown can be debugged by adding the two
level
Values 0x02 and 0x08 together and specifying level as
0x0A.
UniInt Area Hexadecimal Value
Initialization 0x0002
Shutdown 0x0008
Saving to Historian 0x0010
Control Loop Function 0x0020