The need and approach
A machine can operate normally while business software has no visibility into its state, cycle count or faults. Access depends on the PLC manufacturer, model, firmware, communication load and the signals that may be read.
Data flow
PLC → approved read interface → collector → normalised event → application API.
A register address alone does not define a measurement. Data type, scaling, signedness, byte and word order, and units must be mapped. Polling frequency is selected with the controller and network load in mind.
Illustrative workflow
A production line exposes running, waiting and fault signals. State transitions receive timestamps. Loss of communication is not classified as machine downtime.
Questions for discovery
- What are the PLC model and firmware?
- Is a documented register or tag list available?
- Is the scope read-only or are writes required?
- What polling load is acceptable during production?
- Who authorises access and maintenance changes?
What data can be collected from a PLC?
Operating states, cycle counts, product counters, fault codes and process measurements can be read when those signals exist and access is available. A tag name alone is insufficient: its transition conditions, counter resets and fault-code meanings must be understood.
Prepare the PLC make and model, communication module, network layout and permitted tag or register list. Choosing Modbus RTU/TCP or a vendor-specific interface depends on the access methods the equipment actually provides.
How the integration is verified
Begin with a limited signal set. Compare values with the machine’s local display and inspect running, waiting and fault transitions with timestamps. Interrupt the network connection to verify that machine state and data availability remain separate.
The PLC-to-web-dashboard guide explains the path to an operational screen. Validate signal meanings and counter behaviour before using the data for production indicators.
Limits and field conditions
Read-only access without changes to control logic is preferred. Writes and commands require a separate risk assessment and site approval.
Common questions
Can data be collected without changing the PLC program?
It may be possible when a suitable reading interface and access permission already exist. Some machines need an additional communication module, manufacturer support or a program change. That requirement cannot be confirmed before inspecting the equipment.
How do you choose between Modbus TCP and Modbus RTU?
The supported device interface, wiring and network architecture determine the choice. Register mapping, addressing and data types still need validation in either case. Protocol support does not mean that every machine signal is available.
What information is needed for a PLC integration quote?
Provide machine and PLC counts, models, the required signal list, target software, recording frequency and access conditions. Reading data and sending commands to a machine are scoped separately.