Having a spare in stores doesn’t mean you can restart the machine.

That’s harder to accept than it sounds. Most sites that run ELAU PacDrive lines have something on the shelf: a drive, a servo amplifier, a controller from a decommissioned machine that seemed too valuable to scrap. That stock feels like insurance. The question worth asking is whether any of it would actually bring your line back up today, on the specific machine that stopped.

So instead of asking “do we have a spare?”, the question that matters is: “do we have the right spare, at the right firmware, with a verified configuration backup, for the machine currently in service?”

Those are different questions. And on a PacDrive line, the gap between them can be the difference between a two-hour recovery and a two-day one.

Why “We’ve Got Stock” Falls Short

The standard response to obsolescence risk is procurement. Order more before availability disappears. It’s a rational instinct, but it misses three things that matter specifically with PacDrive.

Firmware version incompatibility. PacDrive ties hardware and firmware together tightly. A replacement drive carrying an incompatible firmware version may power up but refuse to synchronise correctly with the controller, or synchronise poorly enough to trigger a following error on the first production cycle. Knowing firmware on the machine and preparing your spare controller’s firmware is what separates a working swap from an extended fault.

Missing or outdated configuration backups. A hardware-compatible, firmware-matched spare still needs the correct parameters loaded before it will run the machine. Clients need to make sure that they have a backup of the card (that is used in the controller), with spare cards on hand.  Having spare cards makes it easier to transition from one controller to another because if a controller fails you can pull out the card and put it in the spare.  

The ELAU PacDrive Obsolescence Timeline

PacDrive M was declared obsolete in December 2018, with no new parts being manufactured. But there are still plenty of machines worldwide running on legacy PacDrive M controllers, producing food, packaging medicine, and filling bottles every shift [2].

The supply of parts hasn’t disappeared. It has shifted. Every available component now comes from refurbished stock, remanufactured units, or the shrinking pool of genuine used parts drawn from decommissioned machines. That pool narrows each year. Price and lead time reflect it.

There’s a second dimension that often goes unexamined: obsolete stock already on the shelf. A site that upgraded a machine from one controller model to another several years ago may still be holding spares bought in anticipation of a configuration that no longer exists on-site. Cash tied up in components that match nothing currently running. The stores list says they’re spares; the machines they once covered have moved on.

Three Questions, Every Spare

A workable framework for managing ELAU PacDrive obsolescence runs three questions against every component before a breakdown, not during one.

Is this part still relevant? Does it match a controller, drive, or motor that is physically running on-site in its current configuration? If a machine has been upgraded, the spare it once covered may no longer serve any live asset. Relevance needs to be checked against what’s running now, not what was running when the part was ordered.

Is it compatible as-is? What firmware does it carry, and is that what the controller requires? These questions are answerable, but only if the machine’s current specification has been documented somewhere accessible.

Is the configuration captured? Before a spare ever goes into service, a current, verified parameter backup should exist for the machine it covers. A backup created last month is more reliable than one that was created within the last three months. However, it is important to note that this only applies to controllers.

Most sites can answer the first question reasonably well. The second and third are harder to answer confidently without live visibility into what the machines are actually running at any given point.

Where the Spreadsheet Loses Track

Stores planning for PacDrive M has traditionally been a manual discipline. Walking the floor, checking firmware labels, cross-referencing paper records and spreadsheets. The gap is that the spreadsheet doesn’t update itself. A firmware change during a scheduled maintenance window, a parameter adjustment by an engineer on the night shift, a hardware swap during a breakdown. None of these automatically flows back to the stores register.

The controller knows all of it. Machine Analyser reads that data directly and passively from the PacDrive controller, covering firmware versions, hardware configurations, and drive health values, without writing to the machine or affecting production [3]. That keeps the spares record aligned with what is actually running, rather than what someone recorded the last time they updated the spreadsheet.

It also puts obsolescence risk into context. Knowing a component is approaching end-of-life matters more when you can see how hard it is working, what its thermal load looks like, and whether it is already logging warnings. That’s the difference between ordering a spare because the calendar suggests it and ordering one because this specific drive on this specific line is showing wear.

Back to Your Stores

Work out three things for your own PacDrive estate. How many of your current spares are formally linked to the specific machines and firmware versions they’re meant to cover? How many of those spares carry a hardware revision you can verify matches your live configuration? And when did you last confirm that the parameter backups for your highest-risk machines are current?

The first question is a stores exercise. The second needs someone to check the machines against the shelf. The third usually requires engineering and stores to talk to each other, and on most sites, that conversation hasn’t happened recently.

The Spare That Actually Works

ELAU PacDrive obsolescence tends to get treated as a procurement problem. Order more before availability runs out. That instinct gets you to the shelf, but it doesn’t get the line running.

The spare that restarts the machine is the one that matches it: right revision, right firmware, configuration verified before the machine stopped. Everything else is just metal waiting for a breakdown that will expose the gap.