Used Robot Handover: What Calibration Records Can and Cannot Establish

A used robot may be offered as an arm, a controller and a teach pendant. Their appearance and model names matter, but a buyer should also ask how the supplied equipment is identified and what calibration-related information is available. A successful power-on demonstration alone does not establish that every file, configuration and application requirement will transfer correctly to a new owner.

Identify the physical equipment in the offer

List the arm, controller, pendant and any other supplied components with their manufacturer and complete model information. Where the manufacturer uses device identifiers to associate components, record them through an appropriate private channel. Confirm that the items shown during inspection are the items included in the agreement; a replacement between demonstration and delivery should be documented.

Universal Robots' C215 error documentation describes a calibration checksum mismatch for its documented system and directs the reader to check the arm and control-box serial association. This is a specific manufacturer example, not a rule that all robot brands use the same files or error codes.

Ask what the records cover

Request a description of available configuration, maintenance and calibration records, including the equipment to which each record relates and the date or version. A document labelled “calibration” may refer to different activities: factory kinematic data, a tool setup, a measurement certificate or a cell-specific alignment. Ask the manufacturer or qualified service provider to explain the document's purpose and applicability.

Do not treat the existence of a file as proof that the robot meets the buyer's positioning requirements. Nor should the buyer assume that a file from a different arm can safely be copied across. The appropriate evidence and any verification depend on the equipment, intended application and manufacturer's instructions.

Backups and support files are not the same as an acceptance test

Universal Robots' support-file guidance explains that certain software versions can export a package containing logs, configuration and calibration information. Its listed contents vary by software platform. Such a file can help authorized support personnel investigate an issue, but exporting it does not itself establish the robot's condition or approve a customer's application.

Before any reset, storage replacement or software change, ask the manufacturer and the responsible technician what information must be preserved and how the action affects the equipment. Do not erase a controller or replace calibration files merely to simplify a sale. Those actions can affect the buyer's ability to assess or use the system.

Agree on access and confidentiality

Robot backups can contain programs, logs, configuration and information about the seller's production process. The parties should agree which materials may be transferred, which contain third-party rights and how sensitive data will be handled. A seller can provide evidence through a qualified intermediary or an approved review process where direct transfer of an entire archive is inappropriate.

For a fictional transaction, a buyer wants confirmation that an arm and controller belong together, while the seller does not want to disclose customer programs. The parties can ask the manufacturer or a qualified service provider what evidence is needed and what can be shared. This example does not establish that a particular inspection or redaction method is sufficient.

Define the demonstration and its limits

Record what was demonstrated, under what conditions, with which components and who witnessed it. A simple motion demonstration may reveal that a system can run a selected program under those conditions. It does not by itself establish accuracy throughout the workspace, remaining life, or safety of a new tool and workcell.

If the buyer needs evidence of a specific performance characteristic, agree on the test method, responsibility and acceptance criteria in advance. The test should be appropriate to the equipment and application, and carried out by qualified personnel under applicable safety procedures. A catalogue specification is not a substitute for that agreement.

Resolve gaps before handover

List missing files, uncertain component associations or outstanding support questions as open items. Agree who will contact the manufacturer, who bears any inspection cost and what happens if the evidence cannot be obtained. The buyer can then assess the commercial implications without treating an unknown as a confirmed defect or a confirmed pass.

The handover record should identify the date on which each item was checked and the person or organization that supplied the information. If a service provider later replaces a component, retain that event with the equipment's history. This helps a future owner understand which configuration was inspected and avoids relying on an old document after the system has changed.

Where the seller offers a warranty, ask whether its terms cover inspection, missing records or configuration work. Warranty wording is a contractual matter and may not guarantee a particular technical result. Seek suitable commercial or legal advice for the actual transaction when needed.

For related transaction records, see why a factory reset is not a complete handover and identifying the controller and teach pendant together. Further guidance is in the used robot section. This article does not provide calibration, reset or installation instructions.