At contract manufacturing sites in India, equipment from European, U.S., and Asian vendors often operates side by side. This article explains how to choose an OPC server that fits your equipment, organized by device type. Details on Mitsubishi PLCs are already available, and coverage of other manufacturers will be expanded in phases.
Not all OPC servers are the same. Because communication standards differ by manufacturer, selecting a product that can get the most out of your equipment is important.
With the discontinuation of MX OPC Server, companies need to review alternative ways to connect with upper-level systems. For example, MELSEC iQ-R can be configured with a Mitsubishi-provided OPC UA server module, while in mixed environments, an external OPC server is a strong candidate. The dedicated page explains how to compare and select alternative options in detail.
In addition to conventional memory access via FINS, selecting an OPC server that can support seamless tag-based access via EtherNet/IP (CIP), which is common in the NJ/NX series, helps ensure smoother integration. With a product that allows integration settings to be configured simply by selecting variables, you can reduce the workload during system setup.
When connecting with upper-level systems, key points include configuration flexibility for connection methods such as EtherNet/IP and MC Protocol, and communication performance that enables high-speed collection of large volumes of data. Based on the required communication method and data volume, it is important to choose an OPC server that is easy to configure and supports real-time data collection.
Logix-family controllers, represented by ControlLogix, have complex, hierarchical tag structures. For this reason, a feature that can automatically browse tags inside the PLC from the OPC server side is an advantage during configuration. Automatic tag browsing can help reduce the burden of manual configuration.
S7-1200/S7-1500 can be configured to use CPU-side OPC UA functions, while PC-side software or dedicated drivers may be required depending on the connection method and operational requirements. By selecting a product that can connect directly via S7 Protocol for the CPU and configuration in use, you can build the system while keeping additional costs under control.
For specialized equipment other than PLCs, such as CNCs and peripheral devices, support for dedicated protocols must also be considered. Because many devices use proprietary specifications, selecting a product with dedicated drivers is essential.
For CNCs, you need to check whether the OPC server supports machine-tool-specific communication methods such as FANUC FOCAS and Mitsubishi CNC EZSocket. In practice, only a limited number of OPC servers support each dedicated communication method as a standard feature. In addition, multiple protocols may coexist, such as Modbus for temperature controllers and EtherNet/IP for industrial robots, so selecting a product with multi-protocol support is required.
The key to selecting an OPC server is understanding the following four requirements in advance.
Even for the same PLC, specifications can differ, and failing to check them in advance may lead to connection problems. Start by clearly identifying the configuration requirements of your company’s equipment. Then, selecting an OPC server product with drivers that support each of the four conditions is the first step toward a smooth deployment.
Connects with PLCs, robots, and machine tools from 100+ manufacturers and 400+ device series.
Existing control devices can stay in use, even in mixed-generation environments.
Without modifying equipment, you can use OPC server-side scripting to shape data and apply equipment recipe data.
The scripting function is available at no additional cost.
Packaged licensing* for large-scale standardization reduces the need to procure licenses when adding new sites or manage updates site by site. This supports scaling while maintaining the management framework.
With add-on options, OPC servers running at different sites can be centrally managed from the main site.
Collects oil and gas drilling data via OPC. Secure transmission across firewalls and redundancy help maintain an audit-ready data foundation over time.
All servers include diagnostic logging with log-level settings and filtering. The logs can also serve as a foundation for audit trails.