Line down on EOL: retrofit before buying a new machine
When the line is down and the OEM recommends a new machine, pressure rises. Many teams buy too early — even when the technical cause is a single EOL node, a protocol break, or a firmware gap.
The wrong default
Symptom → full replacement.
It shortens the internal debate, but often burns CAPEX and months of integration — without checking whether mechanics and periphery still have years left.
A better flow (4 steps)
-
Symptom and scope
Which axis/station? Since when? Which fault? What did the OEM say? -
Reconstruct the technical cause
Bus/protocol, EOL part, control, interface — with measurements and RE where needed. -
Document options
Surplus / repair / targeted retrofit / full replacement — each with effort, risk, and supply. -
Decide with a time horizon
Six months vs. five years of runtime changes the right choice.
When retrofit typically wins
- Mechanics and process are still economic
- The bottleneck is an unobtainable drive, servo, I/O, or firmware state
- Security / CRA / update requirements are rising anyway
What a first assessment should deliver
Not a sales deck: a clear cause (as far as possible), 2–3 options with rough effort, and what now ends downtime vs. what prevents the next failures.
Retrofit service company
Looking for a partner: Retrofit service company · Service Retrofit Service
Bottom line
Downtime is a signal to decide, not automatically to buy new. A solid retrofit decision starts with the technical cause — not the OEM catalog.