PLC Communication and Server Integration
We carry line status and coordination information between PLCs, and monitoring and reporting data between PLCs and servers. Before choosing a method, we examine the PLC model, firmware, data types, connection capacity and control cycle.
Siemens S7Modbus TCPData contractRead-only access
What problem does this service solve?
The question “Can we get this data from the PLC?” going unanswered
An integration built without knowing which block holds the variable, which protocol is enabled and how the read load affects the PLC cycle works for a while. Then it turns into a maintenance problem.
Every application connecting to the PLC separately
When reporting, MES, dashboard and maintenance applications each connect to the same PLC separately, the PLC’s connection capacity can fill up and it becomes unclear who is accessing what.
Controllers from different brands that cannot talk to each other
Without a common protocol, addressing and data type mapping, signal exchange between lines runs over extra cabling or fragile workarounds.
Uncontrolled write operations
Writing recipes or commands from a server to a PLC creates production and safety risks if enabled without defining permissions, approval and logging. Nobody can trace who wrote which value.
What we cover, and within what limits
PLC integration is two separate jobs. PLC-to-PLC communication carries status, counter and coordination information between lines; the volume is low and timing matters. Safety interlocks are not part of this service; safety functions remain in the safety system under the responsibility of the machine manufacturer and the plant’s automation team. PLC-to-server integration, on the other hand, carries production, quality and energy data to reporting, MES or analytics applications. In the Siemens S7-1200/1500 family, an integrated OPC UA server may be available depending on model and firmware; in some cases an additional runtime licence is required. In S7 communication, the PUT/GET access permission and optimised block access settings directly determine the outcome. Modbus TCP is a simple and widespread option built into many devices. Which one to use is decided after checking the supported protocols, access licences, network permissions, data volume and security requirements.
Technical scope
PLC and access inventory
Controller model, firmware, enabled communication services, licence status and a list of everything currently connected to the PLC.
Data contract
Variables to be read/written, data type, unit, sampling period, quality information and owner; approved in a single table.
Choosing the method
OPC UA, Modbus TCP, suitable S7 access or a gateway; weighed together with their effect on PLC cycle load and security.
Network and security boundary
Which network, which port and which identity the server uses for access; read-only access and a single collection point wherever possible. Read-only access also adds communication load on the PLC; the read frequency is measured on a pilot connection.
If writing is needed: a separate scope
The default access for data collection is read-only. If recipe or command writing is required, it is handled as a separate project scope with the approval of the plant’s automation team; limit values, approval, logging and rollback methods are defined within that scope.
Testing and commissioning
Verification in a test environment or in a planned window; connection loss and reconnection are tested separately.
Methods of accessing PLC data: a short comparison
The table provides guidance, not a decision. Whether a method can be used on a particular PLC is determined by the model, firmware, licence and project settings.
| Method | Strength | Point to watch |
|---|---|---|
| OPC UA (in-PLC or external server) | Type information, namespace, certificate-based security | For in-PLC servers, model/firmware support and licence; load from node count and publishing interval |
| Modbus TCP | Widespread, simple, built into many devices | No authentication or encryption; the address map and data type conversion must be documented |
| S7 communication (PUT/GET etc.) | Access to existing S7 PLCs without additional hardware | PUT/GET permission and optimised block access settings; the security impact must be assessed |
| Edge gateway | Brings different protocols into a single data model and provides buffering | The gateway itself is also an asset that must be managed |
Prerequisites: what we need to get started
We list missing information and access together in the first meeting and complete them during the survey.
- Access to PLC models, firmware versions and engineering projects
- The business definition of the data to be read (e.g. “line status”, “part count”)
- Approval from the project owner/automation lead if any settings need to be changed in the PLC
- Server environment (Linux/Windows), network location and IT security policies
- Existing OPC servers and licence information, if any
Deliverables
Inventory of PLCs and communication services
Approved data contract (variable list)
The chosen method and the rationale for the architecture decision
List of network access and security rules
Test scenarios and results
Operation and troubleshooting documentation
Representative scenario: collecting counter and status data from three lines on a single server
The goal is to collect part counts, downtime reasons and line status from three lines running S7 PLCs of different generations. The first task is to establish which access path is enabled on each PLC and its licence status. Instead of every application connecting to the PLC separately, a single collection point is set up. Variables are approved in the data contract, access stays read-only and the read load is measured on a pilot connection. Connection loss and reconnection are tried in a planned test.
This is a representative project flow; it is not a real customer reference.
Service summary
OPC UA, MQTT and Data Integration
We read the data model a machine exposes via OPC UA and, in projects that need MQTT, distribute this data to applications through a broker.
Scope limit
We do not develop PLC application software. If data preparation is needed on the PLC side (e.g. a new data block), this change is made by the plant’s automation team or the machine manufacturer with the project owner’s approval. We handle the data contract and the integration side.
How do we proceed?
No step that touches production is carried out until the maintenance window, configuration backup and rollback plan are clear.
Inventory
PLCs, firmware, services and licence status are identified.
Data contract
The table of variables, periods and ownership is approved.
Method and architecture
The protocol, collection point and security boundary are defined.
Implementation and testing
Commissioning in a controlled window; disconnection and reconnection tests.
Documentation
Connection, variable and operating documentation is handed over.
Questions about PLC-to-PLC and PLC-to-Server Integration
Can every PLC send data directly to a Linux server?
The same method does not apply to every PLC and firmware. Supported protocols, access licences, network permissions and data requirements are checked, and OPC UA, Modbus TCP, suitable S7 access or a gateway is chosen accordingly.
Does reading data affect the PLC's operation?
It can. Very frequent sampling, a large number of variables or too many simultaneous connections increase the communication load. That is why the sampling period and number of connections are limited in the design and tested before commissioning.
Can we write values from the server to the PLC?
It may be technically possible. Our default access is read-only. If writing is required, it is handled as a separate scope with the approval of the plant’s automation team; limit values, permissions, approval and logging mechanisms are defined. Safety functions are not part of this integration.
Is it safe to enable PUT/GET access?
PUT/GET opens an access path without authentication that allows writing as well as reading. If it is to be used, it is handled together with network segmentation and access restrictions. Where possible, a method that supports authentication and encryption, such as OPC UA, is chosen.
Work that can be planned together
OPC UA, MQTT and Data Integration
We read the data model a machine exposes via OPC UA and, in projects that need MQTT, distribute this data to applications through a broker.
Edge Gateways and Protocol Conversion
To collect data from machines that use different protocols, we review the existing interfaces, manufacturer support and open data maps.
SCADA, MES and ERP Connectivity
We identify which system production orders come from and where production quantity and scrap data are generated.
Knowledge Center
Technical guides for this service
Let's plan a technical survey for PLC-to-PLC and PLC-to-server integration
Briefly describe your line, your PLC and network equipment and your goal. We will respond with a written proposal covering scope, assumptions and deliverables.
We deliver PLC communication and OT integration work at plants across Türkiye; site surveys and commissioning take place at the plant during maintenance windows that fit the production schedule. Our service areas.