Monitoring for PLC-driven equipment.
Presses, furnaces, moulding and packing lines — what gets monitored, why the mapping matters more than the acquisition, and how to place equipment on the network.
A Siemens PLC and a SINUMERIK control are different things, and conflating them causes real confusion during scoping. SINUMERIK drives machine tools. Siemens PLCs drive presses, moulding machines, furnaces, pretreatment lines, packing lines and special-purpose machines — the equipment that usually has no monitoring at all.
This page is about that second group. It is deliberately about the equipment class rather than a product catalogue, because what matters is whether the tags you need can be reached and agreed.
| Signal | What monitoring derives from it | Where it usually exists |
|---|---|---|
| Cycle running | Running, idle and stopped states with exact durations; availability | Almost always present in the machine's own logic |
| Part or stroke complete | Output counts and cycle-time distribution | A counter in the program, or a sensor at the ram or slide |
| Mode selector | Separates setup from downtime — without it both figures mislead | A selector switch, usually already read by the PLC |
| Alarm or fault bit | Distinguishes a fault stop from an idle stop | Present wherever the machine annunciates faults |
| Process values | Temperature, pressure, flow, current, kWh trended against machine state | Instruments and meters on the equipment |
The data almost always exists already. The work is agreeing which tags represent these concepts, and recording that agreement so it survives the person who made it.
For common device classes — energy meters, temperature controllers, drives — MachineWise carries ready-made read profiles, so devices that have been seen before connect without repeating the mapping exercise.
For plant-specific PLC logic there is no shortcut. The tags that mean cycle running and good part on your press exist only in your program, and mapping them is a conversation between your maintenance team, your production team and ours. Get it wrong and the numbers are plausible and incorrect, which is worse than obviously broken. The method, including the six fields every mapping needs and the four errors that recur, is in PLC signal mapping for machine monitoring.
Acquisition itself is configured by the MachineWise engineering team, and integration is read-only: no tag is written, no logic is modified, and nothing is downloaded to the PLC.
The verification step matters more here than on machine tools. A scaling or word-order error in a mapped value produces a tidy, confident, wrong number — and comparing the dashboard against the instrument on the machine is the only thing that catches it.
You get what the logic knows
If the program never distinguishes a good part from a cycle, monitoring cannot either until the mapping or the logic accounts for it.
No machine-tool detail
Program names, spindle load and feed override belong to CNC controls. PLC-driven equipment does not have them to give.
Program changes can break a mapping
If a tag moves, monitoring reads the old address and reports nonsense that looks reasonable. Keep the mapping with the PLC backup and re-verify after any change.
Two PLC-driven machines on a live dashboard this week.
On a PLC-heavy floor we would usually suggest one readable machine and one hardwired one, because that answers the two questions that shape a full rollout.
Book a free 2-machine pilot →WhatsApp us