Can I collect data from a PLC without additional hardware?

Yes . If your PLC supports OPC-UA, Modbus TCP, or MQTT over Ethernet, you can connect directly via software using an IIoT platform like Meddle. No physical gateway is required for most modern PLCs manufactured in the last 10 to 15 years.

What is the difference between OPC-UA and Modbus?

OPC-UA is a modern, secure protocol with built-in data modeling, encryption , and self-describing tag structures. Modbus is simpler, older, and universally supported but lacks encryption and requires manual register mapping. Use OPC-UA when available; fall back to Modbus for legacy equipment .

How often should I poll data from my PLC?

For most manufacturing use cases, 1 to 5 second intervals are sufficient. High-frequency applications like vibration analysis may need sub-second polling , while energy monitoring works well at 15 to 60 second intervals .

Will connecting an IIoT platform affect my PLC performance?

Read-only data collection through OPC-UA or Modbus has negligible impact on PLC performance. Modern PLCs are designed to handle multiple simultaneous communication partners. The key is to use reasonable polling intervals .

How to Collect Data from PLCs: Step-by-Step Guide 2026

Why PLC Data Collection Matters

Every PLC on your shop floor is a goldmine of operational data. Cycle times, error codes, temperature readings, motor speeds, counters — all of it is sitting inside your controllers right now, but in most factories, less than a third of this data ever gets used. The rest is invisible, trapped in proprietary interfaces that only a technician with specialized software can access.

Unlocking this data is the single highest-ROI step a manufacturer can take toward digital transformation. Once you can see what your machines are actually doing in real time — not what the shift report says they did — everything changes.

The good news is that collecting data from PLCs has never been easier or cheaper. You do not need to replace your equipment, you do not need to install expensive gateways, and in most cases, you do not need to modify your PLC programs at all.

The 3 Main Industrial Protocols Explained

OPC-UA: The Modern Standard

OPC Unified Architecture is the gold standard for industrial data exchange in 2026. It is platform-independent, secure by design with built-in encryption and authentication, and supports rich data modeling that preserves the context and structure of your information. Most PLCs manufactured after 2015 include an OPC-UA server as standard — Siemens S7-1200 and S7-1500, Beckhoff TwinCAT, B&R, Omron NJ/NX series, and many others.

Modbus TCP/RTU: The Universal Legacy Protocol

Modbus is the oldest and most widely supported industrial protocol, first introduced by Modicon in 1979. It comes in two flavors: Modbus RTU, which runs over serial connections like RS-485, and Modbus TCP, which runs over Ethernet. Virtually every PLC and industrial device supports at least one variant of Modbus, making it the universal fallback protocol.

MQTT: The IoT-Native Protocol

MQTT is a lightweight publish-subscribe messaging protocol designed for constrained networks and devices. Unlike OPC-UA and Modbus, which use a client-server request-response pattern, MQTT uses a broker architecture where devices publish messages to topics and subscribers receive them automatically.

Step-by-Step: Connecting to Your PLC

Step 1: Identify Your PLC and Protocol

Start by cataloging the PLCs on your shop floor. For each one, note the manufacturer, model, firmware version, and available communication interfaces. Check the PLC documentation or web interface to determine which protocols are enabled.

Step 2: Configure the Connection

In your IIoT platform, create a new data source and select the appropriate protocol. For OPC-UA, you need the PLC endpoint URL, which is typically something like opc.tcp://192.168.1.100:4840. For Modbus TCP, you need the IP address and port, usually 502.

Step 3: Map the Data Points

Select the variables you want to collect. Start with the most valuable ones: cycle count, machine state (running, idle, alarm), temperature, energy consumption, and any quality-related parameters. A good practice is to start with 10 to 20 data points per machine.

Step 4: Test and Validate

Before rolling out to production, run a validation cycle. Compare the values shown on the IIoT dashboard with the values displayed on the PLC HMI or local SCADA. Check for correct scaling, proper timestamps, and consistent units.

Step 5: Build Dashboards and Alerts

Once data is flowing reliably, create your first dashboard. Start simple: a real-time view of machine states across the shop floor, with color coding for running, idle, and alarm conditions. Add trend charts for the most critical parameters.

Common Mistakes to Avoid

Polling too frequently — Reading every register every 100 milliseconds creates unnecessary network traffic. For most use cases, 1 to 5 second intervals are sufficient.
Not normalizing data — Always define units, scaling factors, and meaningful tag names at the point of configuration, not later.
Ignoring OT security — Use read-only connections wherever possible, implement network segmentation, and ensure the platform uses encrypted communication.
Choosing the wrong protocol — If your PLC supports OPC-UA, use it. Fall back to Modbus only when OPC-UA is not available.

Software-Only vs. Hardware Gateway

The software-only approach, used by platforms like Meddle, connects directly to PLCs over the network using their native protocols. No additional hardware is installed. This is faster to deploy, lower cost, and less invasive. The hardware gateway approach places a physical device between the PLC and the cloud. This approach makes sense when PLCs do not have Ethernet connectivity or when you need local processing at sub-second latency.

For most modern factories where PLCs already have Ethernet ports and internet connectivity is reliable, the software-only approach delivers faster ROI with less disruption.

How to Collect Data from PLCs Without Replacing Your Equipment