Skip to main content
Yaskawa

Repair vs. Replacement for a Failed Industrial Automation Module: What an Independent Sourcing Desk Actually Does

An independent China-based automation sourcing desk does not repair modules in-house. Here is what we do instead: source a replacement, walk the condition ladder, and tell you when the answer belongs to an OEM service centre.

Repair vs. Replacement for a Failed Industrial Automation Module: What an Independent Sourcing Desk Actually Does

We do not repair industrial automation modules in-house. We do not hold an electronics lab, we do not restore firmware, we do not issue a repair certificate, and we do not fit a module you have sent us back to you. What an independent sourcing desk like ours does, when a buyer asks «Можно ли отремонтировать модуль вместо покупки нового?», is to source a replacement part — a tested unit, a documented equivalent-listing, or a current-production cross-reference — and tell you, line by line, which boundary the answer actually sits on. The rest of this article explains the boundary, the alternatives we do offer, and the cases we send you elsewhere.

Why a buyer asks about repair in the first place

Three situations bring a buyer to the repair question rather than to a stock order.

The first is a tight budget on a non-critical line. A 2010 packaging line uses an Omron CP1E PLC, a Yaskawa Sigma-7 servo drive, and a Siemens KTP400 panel. The PLC and the servo are in production; the KTP400 was retired years ago. A buyer weighing a like-for-like replacement faces a higher quote than a repair-style price, and the line itself is in service, not new design. The repair question is the natural pushback on the quote.

The second is a documented equivalent-listing that looks promising. A buyer has read in a public cross-reference that an Allen-Bradley MicroLogix 1100 series B is pin-compatible with series A. Or that a Mitsubishi FR-A800 series A can be replaced by a series B without a parameter re-load. The repair-versus-replace question becomes: should I rebuild the original on the bench, or should I treat the listing as a documented equivalent and source the newer one?

The third is a service contract that the OEM still offers. The OEM has a service centre in the buyer's region, the model is on the OEM's supported list, and the price for a rebuild is lower than a current-production replacement. The buyer is asking us only to confirm there is no cheaper independent path before they ship the unit to the OEM.

These are real questions, and we treat them as real work. None of them changes the answer to "can you repair it for me?": no, that is not a service we hold. But each one changes the shape of what we can put on a quotation.

What "repair" can mean in industrial automation

The word repair covers at least four different services, and buyers use the same word for all of them. Separating them up front matters because the desk that can do one of them is rarely the desk that can do the other three.

Bench swap. A technician opens the housing, identifies a failed sub-component (a capacitor, a relay, a connector), and replaces that sub-component. The module is then powered on for a smoke test. This is the kind of repair a small regional electronics workshop performs.

Component-level repair. A deeper version of the bench swap: reworking the PCB, replacing an encoder chip, reflowing solder joints, re-flashing firmware if the firmware is publicly available. Requires a microscope, an oscilloscope, and a bench with isolation transformers. Most independent desks do not hold this setup.

OEM service centre repair. The OEM rebuilds the module to factory specification, replaces parts that have a defined service life (cooling fans, electrolytic capacitors, contactors on contactor modules), re-loads the firmware at the current revision, and returns the unit with a service report. This is the path that a service contract buys you.

Refurbishment as we use the term. A previously used module that has been bench-tested, with failing parts replaced and the rest of the unit verified. The result is a working module that is not new, and that we will only describe as refurbished if we hold the bench record and per-unit warranty. It is not a repair of a unit the buyer sent us; it is a working unit sourced through the secondary channel.

The four services are different. The line a buyer is asking about — "can you repair the unit I have?" — almost always means bench swap or component-level repair. We do not perform either. The line "can you sell me a working replacement?" is something we do every day. The two questions get blurred; we keep them separate on the quote.

Why we do not offer module repair

Three reasons sit underneath this boundary.

The first is physical infrastructure. Module repair requires a lab — a temperature-controlled bench, a microscope, a reflow station, an isolation transformer, an oscilloscope, and a stock of replacement sub-components for the families we would service. We do not hold that lab, and we do not pretend otherwise on a quotation. A buyer who asks "do you have your own lab" gets the answer no, we do not, and we do not claim to.

The second is liability and traceability. A repair that goes wrong creates a hazard the buyer has to absorb. If a bench-swapped module is installed on a bottling line and fails three weeks later, the buyer does not have an OEM service report to attach to their internal quality record. We do not want to be the desk that puts a buyer in that position. Our service boundary is part of the value we offer, not a limitation to apologise for.

The third is scope. Our scope is sourcing and consolidated shipment — finding parts, verifying what we found, and getting them on a plane or a truck. Adding a repair capability would change the kind of question we are equipped to answer and the kind of liability we hold. We keep the desk focused.

We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened. The same discipline applies to the repair question: if the answer we can give is honest, we give it; if the answer we can give is "this needs the OEM", we say so.

What we actually do when you ask the question

When a buyer messages us with a failed module and asks whether we can repair it, the workflow we run is the same one we run for any BOM line.

The first step is identification. We need the MPN on the module's label, or a clear photo of the module, its label, and any marking visible on the PCB. If the MPN is partly legible or the module is a non-OEM variant, we tell you what we believe the part is and what we based that on, and you confirm before anything ships. This is the same identification path as article 234.

The second step is the condition ladder. We work the answer down three rungs: a current-production replacement in new surplus, a documented equivalent-listing in new surplus or refurbished, or a working used unit pulled from a decommissioned machine. Each rung has a different warranty scope and a different price band; we present them in that order on the quote.

The third step is the boundary check. If the failed module is on a safety circuit, if it carries a third-party certification scope the buyer cannot re-test, or if the buyer is going to install it on a regulated production line that requires an OEM service report, we say so before quoting. The walk-away cases are part of the service.

The fourth step is the consolidation. If the buyer has more than one failed module — common on a panel-shop retrofit — we source each line on its own rung and ship as one consignment with one set of documents. The line-by-line quote is the unit of work.

A concrete case: a Yaskawa Sigma-7 servo drive

A buyer messages us with a failed SGD7S-120A00A servo drive on a 2018 packaging line. The drive is in production; the firmware revision is current. Three options sit on the quote.

The first is a current-production replacement. We source a Sigma-7 SGD7S in the same voltage and current class. The unit ships new surplus, with the manufacturer label intact, with a bench record stating the firmware revision read back from the unit, and with a one-line warranty per the quotation. The buyer mounts it, loads the parameters from the backup file, and the line runs. The axes we can confirm on this rung are: outline and mounting (matched), electrical ratings (matched), terminal layout (matched), and manufacturer label and firmware revision (matched, with the bench record). The axes we cannot confirm by sourcing alone are: program portability from the buyer's existing controller to the same-model drive (the buyer verifies on install), parameter set retention (the buyer verifies on install), and motor-to-drive compatibility on the specific motor MPN (the buyer verifies on install). We name the unknowns because the buyer needs them to commission the unit.

The second is a same-family later revision. The manufacturer publishes current-production revisions of the same drive family (for example, a current SGD7S hardware revision). We source it, quote the firmware revision that ships on the unit, and tell the buyer to verify parameter-file portability against their existing controller program. This is a same-vendor revision, not a cross-vendor or cross-family substitution; the axes we can confirm by sourcing are outline, mounting, electrical ratings and terminal layout; the axis we cannot confirm by sourcing alone is whether the buyer's existing parameter set ports without manual re-mapping. Verify against the manufacturer datasheet and your own qualification process before you commission. The decision belongs to the buyer's engineering team.

The third is a working used unit pulled from a decommissioned machine. A line that has been retired may have a working Sigma-7 drive in the same voltage class. We source it, bench-test it for power-on and basic I/O, and quote it as used with the bench record attached. The price is lower than the current-production replacement; the warranty scope is shorter; the axes we cannot confirm are life remaining on electrolytic capacitors and cooling fan, history of fault codes, and any internal counter that the manufacturer would read at service. If the buyer's engineering team accepts that scope, the line ships.

The fourth path — can we repair the unit you have — is not on the quote, because we do not perform bench-level repair. If the buyer wants the unit repaired, we point them at a Yaskawa-authorised service centre in their region.

Where the boundary is firm

Three cases are firm walk-aways for us on the repair-versus-replace question, and we say so before quoting.

The first is a safety-rated circuit. An emergency-stop relay, a guard-door interlock, a light-curtain controller, a two-hand control module. These devices sit on a machine-safety role with a defined Performance Level or Safety Integrity Level. We decline to source any change to a safety device from our desk. The buyer needs the OEM service centre or the engineering team that holds the safety case; that judgement is theirs, not ours.

The second is a regulated production line with full traceability. A medical device manufacturer, an aerospace Tier-2 supplier, a food line carrying a third-party audit. The buyer's quality system requires an OEM service report or a fully documented OEM-equivalent rebuild. We are not that supplier, and we do not produce the document chain. We will source the replacement part; we will not produce the certificate.

The third is a firmware-locked module that the buyer cannot re-flash. Some controllers and some safety devices have firmware that is signed to the original unit. A replacement module of the same MPN with the same firmware revision can be installed; a replacement module at a different firmware revision cannot, and bench-repair cannot change that. The buyer needs to know this before they buy. We will tell you on the quote which firmware revision we are sourcing; you confirm before it ships.

What we will not promise

We will not promise a fixed repair turnaround. We will not promise a fixed replacement turnaround. We will not promise a fixed transit time. We will not promise a fixed price. We will not hold a unit for a buyer beyond the quote window. We will not issue a manufacturer warranty on a unit we did not buy from the manufacturer. We will not issue an EAC certificate or a TR CU declaration, and we will not refer the buyer to a certification body as if we were one. We will not make a safety-integrity statement on a safety device.

What we will promise is that every line on the quote carries a stated condition (new surplus, refurbished, or used), a stated bench record where the condition warrants one, a per-line warranty per the quotation, and a per-line MOQ. If a line fails the boundary check, we say so before we put it on the quote.

What we need from you before quoting

Send the failed module's MPN, or a photo of the module and its label. Tell us the machine it came from and, if you have it, the manual. Tell us which rung of the condition ladder you can accept. Tell us whether the line is a safety circuit, a regulated line, or a non-critical repair. If the line is one of those three, we will tell you which path belongs to the OEM and which belongs to us.

We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened. The screening happens before the quote is issued, not after the unit is in transit.

For the industrial environment that the replacement has to operate in, we ask the buyer to confirm the ambient temperature range, the ingress protection rating, the supply voltage tolerance, the vibration profile, and the EMC class. These are the axes that determine whether a sourced replacement will survive on the cabinet. We confirm them per line, because a bench-tested unit that passes a smoke test in our shop may still fail at -20 °C in an unheated outdoor cabinet or on a press with 5 g of vibration. The buyer owns these axes; we quote against them.

A note on the axes we cannot confirm by sourcing alone: the parameter-file portability from the buyer's existing controller to a same-family later-revision unit is unknown until the buyer installs it; the internal-counter history (operating hours, fault log, capacitor life) on a used unit is unknown by definition; and the certification scope of the buyer's existing installation (third-party listing, OEM warranty, regulatory audit) is unknown to us unless the buyer declares it. We name these as unknown because the buyer's engineering team needs them in the open before they sign the quote.

A fail-safe case we want to call out: if a same-family later revision sits on a line that the buyer has documented as do-not-substitute (an OEM-warranty production run, a regulated line with a third-party audit, a bottling line with an OEM service contract), we will not put the later-revision rung on the quote. We will source the original hardware revision only, or we will refer the buyer to the OEM. The do-not-substitute decision rule belongs to the buyer; we honour it on the quote.

For procurement context, see our BOM-quoting process and our pre-dispatch photo record. For replacement-parts sourcing on a specific platform, see the Yaskawa brand page. For dispatch posture to Moscow and the Russian regions and CIS destinations, see our shipping terms; quotations are issued EXW, FCA, DAP, or DDP where the quotation states it.

FAQ

Can you repair a PLC, drive or HMI module that I send to you?

No. We do not perform bench-level or component-level repair, and we do not hold an in-house electronics lab. What we do is source a replacement part — a new-surplus current-production unit, a same-family later revision with the buyer verifying parameter-file portability, or a working used unit pulled from a decommissioned machine — and we tell you the condition per line on the quote. For an in-region repair, we point you at the manufacturer's authorised service centre.

Will a same-family later revision of a failed module work in place of the original?

Often, but not always. The axes we can confirm by sourcing are outline, mounting, electrical ratings and terminal layout. The axes we cannot confirm by sourcing alone are parameter-file portability, program portability, and any internal counter the manufacturer would read at service. Verify against the manufacturer datasheet and your own qualification process before you commission. We name the axes we can confirm and the axes we cannot; the decision is yours.

What is the difference between refurbished and used when you are sourcing a replacement?

A refurbished unit has been bench-tested, with failing parts replaced and the rest verified; we hold the bench record and we describe the unit as refurbished only when that record exists. A used unit is a working unit pulled from a decommissioned machine, with a smoke test only; we do not describe it as refurbished. The two carry different warranty scopes per the quotation, and the rung you accept is your decision.

Do you take repair-style questions for safety devices like emergency-stop relays?

No. We decline to source, recommend, or suggest any change to a safety device from our desk, including emergency-stop relays, guard-door interlocks, light-curtain controllers, and two-hand control modules. The Performance Level or Safety Integrity Level judgement belongs to the OEM service centre and to your engineering team. We will point you to the manufacturer's authorised service centre; we will not put a sourced unit on the quote for a machine-safety role.

How quickly will you answer a repair-versus-replace question?

We answer single-line identification and replacement queries the same working day in most cases. A longer list, a list with several failed modules, or a list where the MPN is partially legible takes longer because each line is sourced individually. We do not quote a fixed turnaround as a service guarantee; the response time depends on the line and on how quickly suppliers confirm.

Can you consolidate replacement parts for several failed modules into one shipment?

Yes. Consolidation is part of the normal workflow. We source each line on its own rung of the condition ladder, hold per-line inspection, and ship as one consignment with one set of documents. Lines with different readiness times can either wait for the slowest line or ship in two batches; tell us which you prefer when you confirm the quote.

Will you issue an EAC or TR CU declaration on a replaced module?

No. We are an independent sourcing desk and we do not issue EAC certificates or TR CU declarations. The importer of record is responsible for that part of the clearance, and the documents that travel with the shipment are a commercial invoice and a packing list per the quotation. The compliance posture for a Russia-bound shipment is set out on our shipping terms.

Send us your BOM or the failed module's MPN through the inquiry form, and we will work the replacement line by line — condition, MOQ, lead time, and the boundary cases — within the same working day in most cases.

Data Notes

  • By the aoctrl sourcing desk. Independent industrial automation distributor for the China market.
  • Data through: September 2026. Last updated 2026-09-24.
  • Catalog grounding: Yaskawa Sigma-7 servo drive family (SGD7S) referenced with a same-family later revision rung on the condition ladder; cross-brand examples (Omron CP1E, Siemens KTP400, Allen-Bradley MicroLogix 1100, Mitsubishi FR-A800) referenced as scenario framing, not as cross-reference ledger entries.
  • Independent distributor notice: aoctrl is not an authorised distributor of Yaskawa, Omron, Siemens, Allen-Bradley, Mitsubishi, Schneider, ABB, Phoenix Contact, or any other brand on the catalogue. We source across the secondary market; we do not represent the manufacturers, and we do not make statements on their behalf.
  • Service boundary: aoctrl does not perform module repair, does not hold an in-house electronics lab, does not issue repair certificates, and does not issue EAC or TR CU declarations. Repair of a failed module belongs to the manufacturer's authorised service centre or to a third-party electronics workshop that the buyer selects.
  • Screening: We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened.
  • This article is part of the buyer-intent track (V12 / V03 / V04 — see ru-buyer-prompt-bank.md).
Last updated: September 28, 2026