Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Interface Configuration Utility ICU

Installed services and Dependencies

  • Last UpdatedNov 22, 2022
  • 2 minute read

Installed services provides a list of the services currently installed on this machine. Services upon which this interface is dependent should be moved into the Dependencies list using the arrow button.

  • Use the Add and Remove buttons to move services between the Installed services and Dependencies lists.

The full name of the service selected in the Installed services list is displayed below the Installed services field.

For example, if API Buffering is installed as a Windows service and is enabled, then bufserv should be selected from the list at the right and added to the list on the left. If API Buffering using PIBufss is installed as a Windows service and is enabled, then pibufss should be selected from the list at the right and added to the list on the left. Only one API Buffering choice should be selected, either bufserv or pibufss.

Often interface services also depend on a vendor program, such as the Fisher-Rosemount chipservice. See the interface user guide for details on what dependencies a specific interface may require.

There are three dependencies that the PI ICU provides assistance with: bufserv, pibufss, and tcpip.

  • PI ICU checks to see if bufserv or pibufss is installed as a Windows service and is enabled. If bufserv or pibufss is installed as a service and is enabled, then PI ICU puts bufserv or pibufss in the dependency list for the user before the service is created. If bufserv or pibufss is installed as a service and is enabled and the service already exists without a dependency on bufserv or pibufss, PI ICU prompts you to add bufserv or pibufss as a dependency.

  • By default, tcpip is always added to this list of dependencies by the ICU.

When the PI interface is started (as a service), Windows service control manager verifies that the services listed in the dependency list are running (or an attempt is made to start them). If the dependent service(s) cannot be started for any reason, then the PI interface service will not run.

See the PI Log and operating system Event Logger for messages that might indicate the cause for any service not running as expected.

TitleResults for “How to create a CRG?”Also Available in