TN - IO - 26050410 Common Causes of OI Server Communication Issues

• Document Version: 001
• Applies to Version(s): 2023 R2

Description  

This technote outlines common causes of OI Server communication issues in AVEVA System Platform environments, where data is not updating between PLCs/devices and client applications such as InTouch, Application Server, or Historian.  

Communication problems can originate from multiple layers within the system architecture, including: 

• OI Server configuration
• PLC/Device configuration & network connectivity 
• Licensing
• Client application configuration

Due to this architecture, a structured troubleshooting approach is required to effectively isolate the source of failure and reduce troubleshooting time.

Note: Examples are based on System Platform 2023 R2 SP1 using the MBTCP Communication Driver. The same principles apply to most OI Servers.

Solution Details

Quick Misconfiguration Checklist:

Before proceeding with detailed troubleshooting, verify the following common configuration issues. These account for the majority of communication problems observed in support cases:

• Incorrect Node Name in Access Name - Confirm the InTouch Access Name is using the OI Server PC Hostname or IP address in the Node name field and not the PLC IP Address.
• Topic Mismatch - Confirm the Topic configured in the OI Server Device Group matches the Topic referenced in the InTouch Access Name.  
• Incorrect PLC IP Address in OI Server Configuration - Verify OI Server configuration details such as correct PLC IP address and port. Ensure changes are saved after edit. 
• Port Open vs. Ping Confusion - A successful ping does not confirm that the required communication port is open or that the TCP server is running. 
• Incorrect Application Name - The Application Name must match the OI Server application name (ex: MBTCP), not legacy DAServer names (ex: DASMBTCP) or full OI Server name (ex: OI.MBTCP.1)

OI Server Configuration Checks:

Confirm the OI Server is running and active

• Confirm the OI Server is started in the OCMC
• Restart the OI Server if needed

Start the OI Server by right clicking OI Server → Activate:

Verify the PLC Network Address Configuration

• Confirm the correct PLC IP address is configured in the OI Server PLC Parameters

PLC Network Address Configuration:

Verify Device Group (Topic) Configuration

• Ensure a Device Group (Topic) is configured 
• Confirm the Topic matches the InTouch Access Name exactly
• Ensure configuration changes are saved

Device Group (Topic) Configuration:

Network Configuration PLC/Device Checks:

• Confirm Network Connectivity to the PLC
• Confirm the PLC is in RUN mode
• Verify tags/registers are accessible from an external client
• Ensure protocol (e.g., Modbus TCP) is enabled

Testing Basic Connectivity:

Use the following commands to validate network connectivity:

# Ping the PLC (Windows CMD)
ping <PLC IP Address>

# Test the connection to the PLC IP:Port (PowerShell)
Test-NetConnection -computername <PLC IP> -port <Configured PLC Port>

Interpretation:

TcpTestSucceeded = True → Network connectivity is valid
Ping = False → Network issue
Ping = True + TcpTestSucceeded = False → PLC service, port configuration, or firewall/security issue

Example: Successful Connection

• Port is open and reachable
• No firewall blocking 

Successful connection test:

Example: Unsuccessful Connection

Ping succeeds, but the PLC is not accepting connections on the configured port.

• PLC protocol/service may not be enabled (e.g., Modbus TCP not running)
• Incorrect port may be configured in the PLC program
• Connection may be blocked by a firewall or security settings on the PLC. 

Unsuccessful connection test:

OI Server Licensing Checks:

• Verify OI Server licensing status
• Verify license includes I/O

The OI Server Manager (OCMC) provides visual indicators to identify the current licensing state of each OI Server instance. These license status icons can help determine whether a server is properly licensed, running in demo mode, or operating with limited functionality.

Note: An unlicensed or incorrectly licensed OI Server may run in demo mode or with limited functionality, which can prevent data updates.

OI Server licensing status indicators in OCMC:

If your OI Server is not acquiring a license, please confirm:

• The OI Server is activated and running
• The license server is running
• Your license has been activated
• Your license includes the correct feature for I/O

Application Configuration Checks:

• If migrating to a new system, confirm the tag database has been updated on the new system
• Verify Access Name configuration

Access Name Quick Reference:

Node Name  - IP Address/Hostname of the computer running the OI Server, NOT the PLC IP. This can be left blank if the OI Server is running on the local PC. 

Application Name - Name of the OI Driver application (ex. MBTCP)

Topic Name - Name of the topic configured in the OI Server Device Group/Topic configuration. This must match the topic configured for the OI Driver exactly.  

Access Name configuration example:

If issues persist, additional diagnostic tools such as WWClient, SLSPing, and the OCMC Log Viewer can be used to further isolate communication issues.

AVEVA Diagnostic Utility wwClient:

https://knowledge.insourcess.com/aveva-general-tech-notes/aveva_diagnostic_utility_-_wwclient

Windows Commands for Testing Suitelink Communications (SLSPING):

https://knowledge.insourcess.com/aveva-communication-drivers-tech-notes/essential-windows-commands-for-aveva-ot-environments-

Log Viewer Diagnostics:

The Log Viewer in OCMC can be used to identify errors and diagnostic messages from the OI Server.

Logs can be accessed in:
Operations Control Management Console (OCMC) → Log Viewer → Default Group → Local

What to Look For:

• Communication errors or timeouts
• Connection failures to PLC/devices
• Licensing or configuration-related warnings

Note: Log messages can provide additional insight into communication failures that may not be visible from the client application or basic connectivity tests.

If the issue is not resolved after completing these steps, please contact technical support for further assistance.

 ________________________________________________________________________________________________________