Skip to main content

Enabling and Disabling Plug-in Instances

Each plug-in instance has a startup mode that allows you to control whether and when it is started at runtime.

Changing the Startup Mode​

  1. In the snap-in bar, go to “Plug-ins” and select the desired plug-in category.
  2. In the instance list, select one of the following values from the “Start mode” column:
    • “Always On” (default): The instance always starts.
    • “Auto”: The instance starts only as long as at least one active connection is using it. The display also indicates whether the instance is currently in use.
    • “Disabled”: The instance does not start.
  3. Alternatively, set the startup mode using the instance’s context menu.
Note:

The “Auto” startup mode does not detect when the plug-in instance is being used from within OPC Router scripts. If the instance is used exclusively in this manner, set the startup mode to “Always On”.

The change will not take effect until you have put the configuration into production.

A deactivated instance is marked in the plug-in tree by a red line across its icon.

Behavior of Connections with a Deactivated Plug-in Instance​

Flows that use a deactivated plug-in instance remain active and are not deactivated along with it. Instead, affected transfer objects display the status “Plug-in disabled” in the status chart as long as the instance being used is deactivated.

For the “Auto” startup mode, every activated flow and every activated template counts as one usage, regardless of the startup mode of the other plug-in instances being used.