Interface startup parameters, Startup options, Conventions and limitations – Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide User Manual

Page 9

Advertising
background image

UniInt Interface User Manual

3

Interface Startup Parameters

Startup parameters determine the behavior of an interface. This chapter documents the
available startup parameters for a UniInt based interface. Consult the interface specific
documentation to discover which parameters are and are not supported by a particular
interface.

Startup Options

Interface startup parameters can be specified using any one of the following three methods:

 Manually enter a series of parameters on the command-line.

 Create a startup file that contains a series of parameters. Issue a command to run the

startup file.

 Create a startup file that contains a series of parameters. Start a service that runs the

command file.

Conventions and Limitations

A Windows command file name must have a .bat extension.

There is no limit to the number of parameters in a startup command file. The maximum line
length in Windows is 1024 characters (1 kilobyte). The maximum length for a parameter in
Windows is also 1 kilobyte.

Continuation characters allow specifying parameters over multiple lines. The continuation
character for Windows is ^ (up arrow caret).

Command-line parameters can begin with a

/

(forward slash) or with a

-

(dash). For

example,

/ps=M

is equivalent to

-ps=M

. Command-line parameters that contain spaces must

be enclosed in double quotes (―). For example,

/path=C:\pipc\interfaces

is a valid

parameter but

/path=C:\Program Files\Rockwell Software\FactoryTalk

Historian\PIPC\interfaces

will not be parsed correctly because of the space in the

path. In order for the path parameter to be parsed correctly, either the value or both the
parameter and value must be surrounded by double quotes. For example, both of the
following are valid parameters:

"/path=C:\Program Files\Rockwell

Advertising