Operations Integration (OI) Servers are the updated version of DA-Servers, providing support for newer PLC models and firmware. They include new features, such as the ability to run multiple instances of the same type on a single node (multi-instance) using the new OI Core. While they offer improved hardware support, the PLC-related code-base remains the same, making them an evolution rather than a completely new product.

Further, OI Servers are transitioning to the Communications Driver Pack, which combines all the new OI-Server releases into a single installer. This pack maintains the same code base for PLC communications, with the addition of bug fixes, enhancements, and support for new hardware.

This document will explain what is needed to upgrade DA-Servers to OI-Servers

• Licensing Requirements
• Migrating DA-Server configuration to OI-Server
• Updating Client Applications

APPLIES TO

• Communication Drivers

EXPLANATION

Section 1 – Licensing Requirements

DA-Servers use an older file-based licensing system. ArchestrA.lic files are used to license them. OI-Servers use Activated licenses in the form of .XML licenses. These are activated via the AVEVA Enterprise License Manager/License Server. For more information on the activated licensing system, please see ISS Training Document 009 – AVEVA Enterprise Licensing Overview.

For older OI-Servers, an OI Servers Standard or Professional license is required. For Communication Drivers Pack OI-Servers, a Communication Drivers Pack license is required.

For pricing questions and licensing options, please speak with your sales representative.

Section 2 – Migrating DA-Server Configuration to OI-Server Configuration

Once you have installed the OI-Server, you will need to configure it. OI-Servers can coexist with DA-Servers, so any existing DA-Servers will not automatically migrate.

Most of the OI-Servers can use the same configuration set as the DA-Servers. There are some exceptions, so it is recommended to check with a technical support specialist and take backups before deciding to use this process. For information on backing up and restoring DA-Server and OI-Server configuration sets, please see ISS Tech Note 54.

Section 3 – Updating Client Applications

Once the OI-Server has been configured and licensed, the last step will be to update any client applications.

When referencing an OI-Server in a client application, you can verify the required name by going to System Platform Management Console/Operations Control Management Console -> OI Server Manager -> Default Group -> <Computer> -> OI Supervisory Servers -> Select your desired OI-Server -> OI.<AppName>.#

In this format, you will use the <AppName> anytime an OI-Server is being used in a client application. See below for an example.

All existing DA-Server configurations will need to have the Application Name updated. This includes, but is not limited to, InTouch Access Names, Application Server DDESuiteLinkClient Objects, and Historian IDAS’s.

The post Upgrading from DA-Servers to OI-Servers appeared first on Industrial Software Solutions.

The AVEVA Operation Integration (OI) Servers are communication drivers used to allow AVEVA software products to communicate with external field devices such as PLCs. The most recent release of the OI-Servers are included in the AVEVA Communication Drivers Pack. This training document will explain how to install and configure an OI-Server, using the OI-MBTCP server as an example.

• Installing the OI-Server
• Configuring the OI-Server

APPLIES TO

• Communication Drivers

EXPLANATION

OI-Servers are the I/O Access Servers utilized by AVEVA products. Since each field device has its own unique language and rules, the field devices need an I/O Access Server in order to actually connect to AVEVA products. The OI-Servers essentially act as a translator converting the field device information back to AVEVA products via a high-speed communication protocol known as SuiteLink.

OI Server Manager

Once the OI-Servers of your choice are installed, they can be accessed in the System Platform Management Console (SMC), within the Operations Integration Server Manager.

NOTE: System Platform Management Console has been renamed in v2023 to Operations Control Management Console (OCMC).

Within the OI Server Manager, you can configure, diagnose, activate, and deactivate OI-Servers. Within the OI Server Manager console tree, the hierarchy contains Server Groups and Server Instances.

Server Groups

A server group consists of multiple server instances that utilize the same OI Server protocol, such as Modbus-MBTCP. When installing a specific OI Server on a computer, the OI Server Manager automatically creates a server group and default server instance for that OI Server. Each OI Server is limited to one server group per computer node. The location of the server group within the OI Server Manager depends on the type of OI Server.

Server Instances

Each server instance has its own configuration, diagnostics, and can be activated or deactivated independently. It appears as a separate application to external clients. When installing an OI Server on a computer, the OI Server Manager automatically creates a server group and a default server instance. The default server instance’s name is based on the short name of the installed OI Server (e.g., OI.SIM.1 for Simulation OI Server). All server instance names follow a similar format.

The middle part of a server instance name becomes the application name used by external clients to access OI Server data. For example, if a server instance is named OI.SIM_0001.1, the corresponding application name would be SIM_0001.

IMPLEMENTATION

NOTE: This document will be using the latest Communication Drivers Pack, version 2023.1. An account on AVEVA’s Support Site is required. Ensure your other software products are compatible by checking the Technology Matrix.

Section 1 – Installing the OI-Server

1. First, download the Communication Drivers Pack. Make sure to unblock the file immediately after downloading by right-clicking the installation media -> Properties -> uncheck the “unblock” button under the Security header if it is there.

2. Once unblocked, move the installation media to the computer of your choice and run setup.exe with Administrator privileges.

3. The installer opens. If you have any existing components such as licensing that are older than the version that will be introduced with the pack, the installer notifies you that it will upgrade those components. Click OK if applicable.

4. Read and accept the license agreement and click Agree.

5. Under AVEVA Communication Drivers Pack, check the box for each driver you want to add. For this document, check “Modicon – MBTCP” and click Next.

6. The next page shows you each item that will be installed. Confirm the list and click Install.

7. Once the product finishes installing, follow any remaining pop-up window prompts to finish the installation.

Section 2 – Configuring the OI-Server

NOTE: If you followed Section 1 or have System Platform 2023 or newer installed, the SMC is now the OCMC.

The following section will walk through configuring a generic modbus device. For information on configuring other OI-Servers, please see their respective product documentation. You can access the Help by right-click any parameter -> Help.

1. Open the SMC/OCMC under Windows -> AVEVA. In the SMC, expand Operations Integration Server Manager ->Default Group->Local->Operations Integration Supervisory Servers -> Modicon – MBTCP -> OI.MBTCP.1

2. Expand OI.MBTCP.1 -> Configuration. Right-click Configuration -> Add TCPIP_PORT Connection

3. Name the TCPIP_PORT connection “Port”.

NOTE: MBTCP uses port 502 as the default port number to contact the PLC which is not configurable at this step. Generic Modbus PLCs can configure a new port, but any controllers configured under the ModbusBridge object (which we will use in this training document) always use port 502.

4. Right-click “Port” -> Add ModbusBridge Connection and name it “Bridge”. Configure the Network address for your PLC.

5. Right-click “Bridge” -> Add ModbusPLCRS Connection and name it “ModbusPLC”. The following options can be configured in Parameters, depending on your device specifications:

PLC unit ID: Modbus Device ID

• Minimum value is 0, maximum value is 255, default value is 1.

Reply Timeout: Amount of time in seconds that the server will wait for acknowledgement

• Minimum value is 1, maximum value is 60, default value is 3.

Use Concept Data Structures (Longs) and (Reals): Read data from the PLC in concept data structure format for “Long” and/or “Real” item types.

Support multiple coil/register write: Select for the PLC to write to multiple coils or multiple registers in one message. If not checked, the PLC will write to a single coil or a single register in one message.

Use Zero Based Addressing: Use 0-based addressing. Uncheck to use 1-based addressing.

Swap Bytes and Swap String Bytes: Select the first to swap bytes in PLC for Long and Real datatypes. Select the second to swap bytes for String datatype.

Bit Order and Register Order: Order of the PLC bit registers and memory registers written to and read from.

Register size (digits): Select the correct register size for addressing the PLC. Determines the maximum address range.

• 6-digit is the default value.

String Variable Style: PLC string-data format.

Register Type: Binary or BCD

Block I/O Size: Choose the maximum number of:

• Discrete inputs/coils to read at one time
• Coils to write at one time
• Extended registers to read at one time
• Holding registers to write at one time

6. Click Device Groups. Right-click the empty space -> Add to add a new topic. This defines the rate at which items will be polled by the PLC.

7. Click Device Items. This is an optional parameter where “Alias” names can be assigned to items in the PLC. For example, you can assign register 30001 to the name “Mixer100.PV”. Then, when you are creating a tag or attribute to pull a value from 30001, you can configure the item reference to be “Mixer100.PV” instead of the register name.

8. The OI-Server configuration can now be saved. To start the driver, right-click OI-MBTCP and choose the activation type of your choice.

The post Installing and Configuring OI-Servers appeared first on Industrial Software Solutions.