/dl=#
Optional
|
Where # specifies the delay in seconds between bailey get exceptions.
Default = 1 second
Minimum = 0.1
Maximum = none
|
/ec=#
Optional
|
The first instance of the /ec parameter on the command line is used to specify a counter number, #, for an I/O Rate point. If # is not specified, then the default event counter is 1. Also, if the /ec parameter is not specified at all, there is still a default event counter of 1 associated with the interface. If there is an I/O Rate point that is associated with an event counter of 1, each copy of the interface that is running without /ec=# explicitly defined will write to the same I/O Rate point. This means that one should either explicitly define an event counter other than 1 for each copy of the interface or one should not associate any I/O Rate points with event counter 1. Configuration of I/O Rate points is discussed in the section called “I/O Rate Tag Configuration.”
|
/ef=#
Optional
|
This parameter controls the exception screening behavior of the ICI module. Exception screening is enabled when /EF=1, in which case the INFI90 sends only deviation exceptions, no maximum time exceptions. Though this feature will significantly reduce the communications traffic, it can prevent the PI system from reconstructing the data between two exception reports accurately. For example: if a value changes slowly, then Bailey would not send the change until the total change exceeded the deviation limit. Therefore, one cannot distinguish a step change from a linear change. Hence, this option is set to 0 by default. The /EF=1 parameter is primarily used for system with mostly digital or discrete data.
Default = 0 (disabled)
Minimum = 0 (disabled)
Maximum = 1 (enabled)
|
/evg=#
Optional
|
Define the Event Logger group to be used when ASCII data (type 30) is sent to the Event Logger. Where # is the group number.
Default = 4
Minimum = 0
Maximum = 1000
|
/evt=#
Optional
|
Define the Event Logger type to be used when ASCII data (type 30) is sent to the Event Logger.. Where # is the type.
Default = 11
Minimum = 0
Maximum = 1000
|
/fm=#
Optional
|
This parameter controls the failover mode of the interface. Specify
/FM=0 for no failover
/FM=1 for the primary interface
/FM=2 for the secondary interface. Also, for the secondary interface, the PCU number of the ICI mode communicating to the primary interface must be supplied. The details of the failover mechanism are described in Failover Operation section.
Default = 0
Minimum = 0
Maximum = 2
|
/fp=#
Optional
|
The failover primary PCU address is required only if failover is used, and this is the secondary interface
Default, not defined.
Minimum = 0
Maximum = 2147483647
|
/fs=#
Optional
|
/FS=# specifies the SYSTEM digital state integer value to replace an analog value that is greater than the analog filter limit specified by /FV=#. This parameter has no affect if /FV=# is not specified.
Default = 248 (No Data)
Minimum = 0
Maximum = 1024 or maximum SYSTEM digital state value
|
/fv=#
Optional
|
/FV=# specifies an analog filter limit in integer or floating point with decimal format. If an analog value from Bailey is greater than this value, the interface will be replace it with the digital state code specified in /FS=#. The FV parameter must be greater than 1000 to be considered valid by the interface. If /FV is not specified, no analog filter checking will be performed by the interface. If /FS=# is omitted, the interface will default to /FS=248 (NO DATA) as the digital state to substitute for the analog value over the filter limit.
Range {0,1001 – n )
Default = 0 (disabled)
Minimum = 1001.0
Maximum = None
|
/icdb
Optional
|
Even though the Bailey semAPI is designed to handle multiple user clients, PI Bailey semAPI interface expects exclusive control of the ICI device, specially the configuration of the point table on the ICI. If the interface is started in trouble-shooting mode (/ICDB), the user can simultaneously communicate with the ICI via Bailey’s TALK90 program. This can be a useful debugging tool for determining the current condition of the ICI. During normal operation, this option should not be checked.
Default, not defined.
|
/ici=#
Optional
|
Where # specifies the Bailey logical ICI number, set to interface ID number if not defined.
|
/id=x
Required
|
The /id parameter is used to specify the interface identifier.
The interface identifier is a string that is no longer than 9 characters in length. UniInt concatenates this string to the header that is used to identify error messages as belonging to a particular interface. See the section called “Error and Informational Messages” for more information.
UniInt always uses the /id parameter in the fashion described above. This interface also uses the /id parameter to identify a particular interface copy number that corresponds to an integer value that is assigned to Location1. For this case, one must use only numeric characters in the identifier. For example,
/id=1
|
/host=host:port
Required
|
The /host parameter is used to specify the PI Home node. Host is the IP address of the PI Sever node or the domain name of the PI Server node. Port is the port number for TCP/IP communication. The port is always 5450 for a PI 3 Server. It is recommended to explicitly define the host and port on the command line with the /host parameter. Nevertheless, if either the host or port is not specified, the interface will attempt to use defaults.
Defaults:
The default port name and server name is specified in the pilogin.ini or piclient.ini file. The piclient.ini file is ignored if a pilogin.ini file is found. Refer to the PI API manual for more information on the piclient.ini and pilogin.ini files.
Examples:
The interface is running on a PI Interface Node, the domain name of the PI 3 home node is Marvin, and the IP address of Marvin is 206.79.198.30. Valid /host parameters would be:
/host=marvin
/host=marvin:5450
/host=206.79.198.30
/host=206.79.198.30:5450
|
/hncc
Optional
|
This option must be specified if connecting to an HNCC as opposed to an ICI03.
Default, not defined.
|
/me=#
Optional
Default:
/me=2500
|
Maximum number of exceptions per iteration as defined by /dl=# parameter.
Default = 2500
Minimum = 100
Maximum = 2147483647
|
/mp=#
Optional
Default:
/mp=30000
|
The maximum number of points for this interface.
Default = 30000
Minimum = 1
Maximum = 2147483647
|
/of=#
Optional
|
Enable outputs from PI to Bailey
Default = 0 (disabled)
Minimum = 0 (disabled)
Maximum = 1 (enabled)
|
/ps=
Required
|
The /ps parameter specifies the point source for the interface. The is not case sensitive and can be any single or multi character string. For example, /ps=P and /ps=p are equivalent.
The point source that is assigned with the /ps parameter corresponds to the PointSource attribute of individual PI Points. The interface will attempt to load only those PI points with the appropriate point source.
|
/q
Optional
|
When the /q parameter is present, Snapshots and exceptions are queued before they are sent to the PI Server node.
The maximum queue size is 255 bytes for a PI 3 Server and 36 bytes for a PI 2 Server. For example, if the interface is running on a UNIX node and is communicating to a PI 2 Server, then the maximum queue size is 36. The queue is flushed between scans if it is not filled.
When the /q parameter is specified in non-extended API mode, the PI API sends integer values as 16-bit integers instead of 32-bit integers. Therefore, integer points will be limited to values between 0 and 32767. Values higher than 32767 need to be sent to floating-point PI tags.
|
/rc
Optional
|
When defined, Range Checking enabled at interface level. All analog values above (Zero + Span) will be replaced with the digital state OverRange. All analog values below Zero will be replaced with the digital state UnderRange.
Default, not defined.
|
/sio
Optional
|
The /sio parameter stands for “suppress initial outputs.” The parameter applies only for interfaces that support outputs. If the /sio parameter is not specified, the interface will behave in the following manner.
When the interface is started, the interface determines the current Snapshot value of each output tag. Next, the interface writes this value to each output tag. In addition, whenever an individual output tag is edited while the interface is running, the interface will write the current Snapshot value to the edited output tag.
This behavior is suppressed if the /sio parameter is specified on the command line. That is, outputs will not be written when the interface starts or when an output tag is edited. In other words, when the /sio parameter is specified, outputs will only be written when they are explicitly triggered.
|
/stopstat
or
/stopstat=
digstate
Default:
/stopstat=
”Intf Shut”
Optional
|
If the /stopstat parameter is present on the startup command line, then the digital state Intf Shut will be written to each PI Point when the interface is stopped.
If /stopstat=digstate is present on the command line, then the digital state, digstate, will be written to each PI Point when the interface is stopped. For a PI 3 Server, digstate must be in the system digital state table. For a PI 2 Server, where there is only one digital state table available, digstate must simply be somewhere in the table. UniInt uses the first occurrence in the table.
If neither /stopstat nor /stopstat=digstate is specified on the command line, then no digital states will be written when the interface is shut down.
Examples:
/stopstat=”Intf Shut”
The entire parameter is enclosed within double quotes when there is a space in digstate.
|
/to=#
Optional
Default:
/to=90
Maximum:
/to=240
|
This parameter specifies the ICI module watchdog timer. If the interface stops communicating with the ICI module for a period longer than the specified watchdog timer, the ICI module will go off-line, setting all the output points (PI to Bailey) to bad quality. For systems using PI values in the Bailey control loops, the watchdog timer will prevent the old value from being used in the control loop. Also, do not set the watchdog timer to 0 if the interface is set up as failover primary interface. Otherwise, the secondary interface will not pick up data collection when the primary interface stops communicating with the ICI module. See the Failover Operation section for details.
|
/ts=#
Optional
Default:
/ts=0
|
This parameter controls the time synchronization behavior between Bailey and PI systems. Note that the interface cannot change the PI system time. Also, if the interface is linked to a Data Acquisition version of semAPI, the interface cannot set the time on the Bailey System. The time master of the loop is determined by the time accuracy factor on each node. Hence, the time accuracy must be set to 15 or greater on the CIU module through the CIU utilities by connecting a terminal to the CIU termination unit. See the CIU manual for details on how to use the CIU utilities.
/ts=0 disables time synchronization
/ts=1 sets PI time as the master time
Default = 0 (disabled)
Minimum = 0
Maximum = 1
|
