Why projects stall here
There is more than one way out of a machine. No Ethernet may still mean a serial port; no serial may still mean a dry-contact output; and where none exists, an external sensor remains.
What matters is deciding what you want to see first. Starting from "collect everything" turns into surveying dozens of tags per machine and never finishing. If you only need production quantity, one contact often ends it.
Procedure
Following the order matters more than perfecting each step.
- STEP 01
Decide the values you need
Work backwards from the objective. Automating results means the production counter; downtime analysis means stop signals and reasons; quality cause analysis means process conditions. Fewer items, faster survey.
- STEP 02
Survey the communication path per machine
Check communication options on the nameplate and in the manual, then look at the machine for ports. Ethernet and serial ports, contact terminals and any existing external devices are all in scope.
- STEP 03
Choose the collection path
Read the protocol where communication exists; consider RS-485 with Modbus where only serial does. Count pulses where only contacts exist, and attach a proximity or current sensor where nothing does.
- STEP 04
Verify with a trial collection
Connect one machine first and confirm the values match reality — that the counter agrees with actual output and stop signals with actual stops — over a few days before expanding.
Common mistakes
Patterns that recur in implementation discussions.
Common mistakeSurveying every machine simultaneously
Finishing one or two representative machines first makes the remaining survey far clearer.
Common mistakePolling far faster than necessary
Second-by-second collection is not automatically better. It raises communication load and storage while analysis often only needs minutes.
Common mistakeSkipping the equipment vendor
Warranty terms and communication specifications are safer confirmed with the manufacturer, particularly for leased equipment where external connection may be restricted.
Common mistakeTreating sensors as a last resort only
Where communication negotiations drag, attaching a sensor is sometimes both faster and cheaper.
Checklist
Confirm these are in place before starting.
- The collection objective and required values are listed
- Communication ports and contact outputs are surveyed per machine
- Vendor warranty and communication terms are confirmed
- A trial collection is complete on one representative machine
- Collected values have been checked against actual values
- The polling interval matches the analysis objective
Quick AnswersLegacy equipment communication survey — frequently asked
Questions that come up during evaluation.
Do we need to replace equipment to collect data?
Rarely. Without communication you use contacts; without contacts, an external sensor. Replacement is seldom the answer.
Do we have to modify the PLC program?
Reading existing memory areas is usually sufficient. Only when a required value is not defined at all is a change discussed with the equipment owner.
Will reading data slow the machine?
Read-only access does not participate in control logic. An excessively short polling interval does create load, so the interval is set to the objective.
Can leased equipment be connected?
Contract terms come first. Where external connection is restricted, attaching a sensor outside the machine is the usual way around it.
How does this play out in your plant?
Equipment mix and current workflow determine how the procedure is adapted.
Request a site survey