Moxa / MX-AOPC UA Server

Source: MOXA Official website
(https://www.moxa.com/en)

MX-AOPC UA Server connects field devices to SCADA and other OPC client applications. Moxa's Windows-based software combines Modbus polling with Active Tag updates from compatible Moxa devices, allowing different data-collection methods within one installation.

For an Indian plant or distributed monitoring project, selection starts with the field equipment and the required update behaviour. Identify which devices can send active updates and which need to be polled before sizing the connection.

Key Takeaways

• Use Active Tags with compatible Moxa devices; assess standard Modbus devices through the polling route.
• Separate live data collection from database logging and historical-data recovery when defining the software scope.
• Compare Trial, Free and Paid license conditions against the number of connected devices.
• Match the software version to the host operating system, device models and client security settings.

Challenges MX-AOPC UA Server Can Help Solve

Source: MOXA Official website
(https://www.moxa.com/en/products/industrial-edge-connectivity/opc-ua-software/mx-aopc-ua-suite)

Collecting Changed I/O Values with Active Tags

Compatible Moxa I/O devices can send updates when values change or a configured interval is reached. Active Tag communication uses Moxa's AOPC protocol between the field device and MX-AOPC UA Server.

This approach reduces repeated requests for unchanged values. For remote sites, compare event frequency with the required monitoring interval to determine which signals should use change-based reporting and which need periodic updates. Test the resulting traffic with representative field data.

Connecting Modbus Devices to OPC Clients

The server also collects data as a Modbus TCP or Modbus RTU client. This polling route provides a connection for devices that expose data through Modbus registers.

Build a register map covering addresses, data types and access requirements before configuring tags. Active Tag support is device-specific; a Modbus connection alone does not give a third-party device Moxa's push functionality.

How Server, Viewer and Logger Work Together

The Suite assigns different tasks to its components. Server publishes device data, Viewer checks it, and Logger records it.

For network-outage recovery, Moxa documents a combination of compatible ioLogik 2500 devices, local SD-card storage, Server and Logger. Logger retrieves missing records after communication returns. Include the storage and Logger requirements when planning this workflow.

Where Is MX-AOPC UA Server a Good Fit?

Evaluate the server for projects that combine compatible Moxa remote I/O with Modbus equipment and need to deliver the collected values to an OPC application. Distributed facilities should assess network demand and reconnection behaviour alongside normal operation.

A single-site connection and a multi-site monitoring rollout need different tests. Start with representative devices and the intended SCADA client, then repeat the checks with the expected device count and update rates.

Key Specifications and Compatibility

Use version-specific requirements when selecting the host PC. The v2.2 release notes add operating systems beyond those shown in the older datasheet's specification table. Device firmware and the receiving client's supported settings also need to match the proposed installation.

Deployment Example: Natural Gas Wellhead Monitoring

Source: MOXA Official website
( https://www.moxa.com/jp/products/industrial-edge-connectivity/opc-ua-software/mx-aopc-ua-suite)

Moxa describes a Southeast European energy company's use of ioLogik 2542-GPRS remote I/O and MX-AOPC UA Server for natural gas wellhead monitoring. Active messages carry field updates to the control centre's SCADA system when I/O states change or configured events occur.

The project also used the remote I/O's integrated functions to address limited cabinet space. For a comparable installation, assess communication costs together with the hardware, power and enclosure requirements at each field location.

Trial, Free and Paid Licensing

User Manual v4.0 documents three license options. The device limit and registration requirement differ by license.

The paid license's device-count allowance does not define achievable throughput. Size the host and validate the workload separately. For an Indian purchase, request local pricing and registration details from Moxa's sales or distributor channels.

Download, Setup and Tag Verification

Use Moxa's official software resources to obtain the installer and matching release notes. Manual v4.0 is a document revision; v2.2 is the software version referenced in the compatibility information above.

1. Install the software and select the host network adapter.
2. Configure Active Tags on compatible devices, or create Modbus devices and tags in the console.
3. Set the OPC UA endpoint, security policy and certificate trust.
4. Apply the settings using Update Configuration to Server.
5. Open Viewer and check the received tag values.

Configuration edits must be applied to Server Runtime before they take effect. During evaluation, compare values with the field device and test the behaviour after a connection loss before adding the production workload.

Manufacturer Information

Moxa supplies industrial networking and edge-connectivity products. Use its Find a Distributor or Email a Representative options to request local sales assistance for an Indian project.