How to Scope a PLC Data Collection Project Before Choosing an Edge Gateway
Scope a PLC data collection project by defining the exact controllers, physical interfaces, protocol variants, tags, engineering units, scan intervals, quality rules, local processing, and upstream destination before selecting hardware. The Robustel EG5120 is relevant when that path needs industrial serial or Ethernet connectivity, local applications, resilient backhaul, and centralized management. However, a product name or protocol label is not enough: build a representative tag list and acceptance test so the required E2C Factory driver or custom application can be verified against real equipment.
Illustrative project-planning scene using the official EG5120 product image; it is not a documented customer installation.
Key Takeaways
- Define the PLC, interface, protocol, tag meaning, scan interval, and consumer before comparing gateways.
- Test the exact device and data types; a general protocol name does not prove project compatibility.
- Budget local compute, storage, network, and recovery behavior from representative load.
- Use a signed acceptance matrix to align OT, IT, cybersecurity, and application owners.
In This Guide
- What information belongs in a PLC data inventory?
- How should tags and data quality be defined?
- How does the EG5120 support the data path?
- What should the pilot acceptance test include?
- Frequently asked questions
What information belongs in a PLC data inventory?
Start with equipment identity rather than a desired dashboard. Record the controller manufacturer and model, firmware where relevant, network address, physical port, protocol variant, security constraints, cabinet location, and the operational owner who can approve access. For serial equipment, include RS-232 or RS-485 wiring, baud rate, parity, node address, termination, and isolation requirements. For Ethernet equipment, include subnet, VLAN, routing, firewall, and available connection limits.
Next, list the data consumers. A maintenance dashboard, MES transaction, historian, cloud service, and alarm workflow can require different naming, timestamps, quality indicators, and delivery patterns. One PLC connection may feed several consumers, but each relationship must be explicit.
| Scope item | Minimum project evidence |
|---|---|
| Source | Controller, firmware, port, address, protocol, owner |
| Tag | Address, data type, scale, unit, valid range, description |
| Timing | Scan interval, change behavior, timestamp source, latency objective |
| Edge action | Read, normalize, calculate, buffer, alert, or visualize |
| Destination | Protocol, endpoint, topic or namespace, authentication, owner |
| Recovery | Offline behavior, retry, duplicate handling, restart, evidence retention |
This inventory exposes constraints before hardware is ordered. It also helps identify when direct PLC-to-application communication is sufficient and when a local edge layer provides real value.
How should tags and data quality be defined?
A tag list should describe meaning, not only addresses. Include the source address, signed or unsigned type, byte order, scale, engineering unit, valid range, update condition, and quality behavior. Define whether timestamps originate in the PLC, gateway, or destination. State how stale, invalid, unavailable, and out-of-range values are represented.
Scan interval should follow operational need and controller capacity. Reading every point as fast as possible can add network and PLC load without improving decisions. Group points by use case, estimate traffic, and test the real controller. For event or alarm data, define how changes are retained during interruption and how duplicates are handled after reconnect.
Security belongs in the same scope. Identify whether the gateway initiates outbound connections, which ports are allowed, where certificates and credentials live, who rotates them, and how remote troubleshooting is authorized and logged.
How does the EG5120 support the data path?
The official EG5120 product page lists two Gigabit Ethernet ports, two software-configurable RS-232/RS-485 ports, two digital inputs, and two digital outputs. It combines those field interfaces with RobustOS Pro, local compute and storage, dual-SIM cellular options, and RCMS management.
Robustel's E2C Factory documentation describes Modbus TCP and Modbus RTU collection on EG5120 and northbound delivery through options including MQTT or OPC UA. The broader E2C Factory overview describes 100+ industrial protocol drivers and functions for collection, cleaning, analysis, alerts, storage, visualization, and forwarding. Availability depends on the specific gateway, software version, edition, license, and driver. Verify the exact PLC path rather than inferring support from the library count.
If the required driver or data handling is outside the approved E2C path, RobustOS Pro also supports Debian packages and Docker containers. That flexibility transfers application lifecycle responsibility to the project team, including dependencies, resource limits, patching, backup, and recovery.
What should the pilot acceptance test include?
Use one representative PLC and a bounded tag set. Confirm wiring and addressing, then read every selected data type and compare values with an approved reference. Verify scaling, units, timestamps, quality, and invalid-value behavior. Test the intended upstream format and authentication with the real destination.
Run the test through power restart, application restart, WAN interruption, destination outage, certificate failure, and configuration restoration. Observe CPU, memory, storage, logs, polling behavior, buffered data, retries, and duplicates. The pilot should end with a signed tag list, configuration backup, recovery procedure, responsible owners, and a rule for adding new PLCs or tags.
Frequently asked questions about PLC data collection
Can one EG5120 collect from both Modbus TCP and Modbus RTU devices?
Robustel documents EG5120 with E2C Factory for Modbus TCP and Modbus RTU collection. Confirm port counts, network topology, serial settings, polling load, exact data types, software version, and licensing with the representative devices before rollout.
How many PLC tags can an edge gateway collect?
There is no useful universal number. Capacity depends on protocols, scan intervals, data types, controller response, transformations, storage, northbound delivery, and other local workloads. Build a load model and measure it during the pilot with planned headroom.
Should the gateway timestamp PLC data?
The design should name one authoritative timestamp source and define clock synchronization, timezone, outage behavior, and quality. Gateway timestamps can be appropriate, but they should not silently replace PLC event time when sequence or control context matters.
Is a protocol converter enough for PLC-to-cloud data?
It can be when the requirement is a simple, bounded conversion. An edge gateway is more appropriate when the project also needs local buffering, normalization, applications, dashboards, rules, secure cellular backhaul, or fleet operations.
What should you do next?
Create the PLC and tag inventory, then compare it with the Robustel EG5120 and the official E2C Trinity Modbus guide. Contact Robustel with representative device models, register maps, regional requirements, upstream protocol, and acceptance criteria to confirm the hardware and software configuration.
About the Author
Mark, Technical Support Engineer at Robustel
Mark is a Technical Support Engineer at Robustel with practical experience in industrial networking, edge connectivity, and field deployment. He supports customers with solution planning, device configuration, application review, troubleshooting, and technical training across cellular routers, edge gateways, and LoRaWAN systems. His work focuses on turning project requirements into verifiable configurations, repeatable commissioning steps, and maintainable operating practices for global industrial IoT deployments from pilot through long-term fleet operation.
Leave a comment