A second-hand robot inspection should answer a harder question than whether the arm powers up and moves. The real issue is whether the robot can enter a specific production environment without creating avoidable mechanical, controller, compatibility, maintenance, or downtime risk. A machine can look clean, complete a short demonstration, and still be a poor purchase once tooling, commissioning, spare parts, software, and cell integration are considered.<\/p>\n
This is why inspection should follow a sequence. Buyers need to confirm identity first, examine condition second, test operation under meaningful conditions third, and only then judge whether the robot fits the intended cell. Reversing that order encourages decisions based on appearance, purchase price, or a successful no-load movement test.<\/p>\n
The following step-by-step guide is designed for technical buyers, maintenance teams, engineers, and production managers evaluating a used industrial robot. It is not a substitute for manufacturer-specific service procedures or a qualified technical assessment, but it provides a practical structure for deciding what deserves further verification before money and integration resources are committed.<\/p>\n
The first inspection task is not checking paint, cables, or bearings. It is establishing exactly what equipment is being evaluated. Model variants matter because robots from the same family can differ in configuration, controller generation, application package, mounting arrangement, software environment, and other characteristics that affect cell design.<\/p>\n
Record the identification information available on the robot and controller. The objective is to connect the physical equipment being inspected with the documentation, configuration, and intended application being discussed by the seller.<\/p>\n
This step is especially important when a buyer has started with a general requirement such as \u201ca handling robot\u201d or \u201ca welding robot.\u201d A broad family name is not enough for final engineering decisions. Before tooling, layout, payload margin, reach, safety envelope, or interface planning begins, the exact variant should be verified against appropriate manufacturer documentation.<\/p>\n
Buyers comparing second-hand equipment should also distinguish between a used robot and a refurbished robot. Those terms do not automatically describe the same technical condition or scope of work. URT\u2019s guide to choosing between new and refurbished robots<\/a> explains why equipment condition and project context matter more than the label alone.<\/p>\n Use the identification stage to build a traceable equipment record. The goal is to prevent later engineering work from being based on an assumed model, controller, or configuration.<\/p>\n If identity cannot be established confidently, the inspection has already found a purchasing risk. The correct response is not to fill the gaps with assumptions from a similar robot family.<\/p>\n A physical inspection shows the robot\u2019s present condition, but history can explain why that condition exists. Two visually similar robots may represent very different risks if one has a documented service background and the other has an unclear application history, missing backups, or unknown modifications.<\/p>\n Ask what is known about the previous application. A robot used in one process environment may have faced different contamination, duty, collision, cable, or maintenance conditions from a robot used elsewhere. Application history does not prove condition by itself, but it tells the inspector where to look more carefully.<\/p>\n Service history is useful when available, but missing records should be treated as missing information rather than evidence of poor or good condition. The buyer should separate what is documented from what is claimed verbally.<\/p>\n This is also the point to review the broader buying criteria in URT\u2019s guide to what to consider when buying refurbished robots<\/a>. The inspection should support the purchase decision, not become an isolated mechanical exercise.<\/p>\n The available record will vary by machine and seller. Use the following points to identify gaps that may affect commissioning, support, or future recovery.<\/p>\n A lack of documentation does not automatically make the robot unusable. It does increase uncertainty, and that uncertainty should influence the depth of technical inspection and the total project risk assessment.<\/p>\n A clean exterior is not a condition report. Cosmetic preparation can improve presentation without answering questions about joints, reducers, brakes, seals, mechanical damage, cable routing, or evidence of previous impacts.<\/p>\n Begin with a systematic visual examination of the complete arm. Look for conditions that deserve further investigation rather than trying to diagnose every issue from appearance alone. Cracks, damaged covers, missing fasteners, irregular gaps, oil residue, corrosion, impact marks, improvised repairs, or inconsistent components can indicate that the inspection needs to go deeper.<\/p>\n Pay particular attention to areas exposed to movement and process conditions. Dress packs, wrist areas, cable routing points, connectors, and interfaces around tooling can experience repeated motion or application-specific contamination. The practical question is whether visible condition suggests normal use, neglected maintenance, unsuitable repair, or damage requiring specialist assessment.<\/p>\n Axis condition should be evaluated through appropriate testing by competent personnel and in accordance with the relevant equipment procedures. The objective is to identify abnormal behavior, not to improvise intrusive repair work during a purchase inspection.<\/p>\n Listen and observe during controlled movement. Unusual noise, vibration, inconsistent motion, unexpected play, or behavior that changes with direction can justify further investigation. A short, slow movement is not enough to prove mechanical health across the working range.<\/p>\n Brakes also matter because a robot that moves correctly under one simple test may still require deeper evaluation of holding behavior and axis condition. Any test involving safety-critical behavior should be performed by qualified personnel using appropriate procedures.<\/p>\n The wrist is particularly important because application tooling, process cables, impacts, and repeated motion converge around this area. Inspect the visible mechanical condition of the flange area, wrist covers, cable routing, and any included tooling interface.<\/p>\n Do not assume that included end-of-arm tooling is automatically suitable for the next application. Even if the gripper or process tool appears serviceable, its mass, geometry, center of gravity, interfaces, utilities, and production function must be evaluated separately.<\/p>\n The robot arm is only one part of the purchase. A mechanically acceptable arm paired with a problematic controller, damaged pendant, missing hardware, unclear software configuration, or incompatible interfaces can turn an attractive price into an expensive integration project.<\/p>\n Inspect the controller cabinet externally and, where appropriate and safe, have qualified personnel assess its internal condition according to relevant procedures. Look for signs that justify deeper investigation: contamination, corrosion, damaged connectors, improvised wiring, missing covers, unexplained modifications, poor cable entry, or evidence that the cabinet has been stored in unsuitable conditions.<\/p>\n The teach pendant should also be checked as part of the system rather than treated as an accessory. Physical damage, unreliable controls, display issues, cable condition, and connection problems can affect commissioning and operation.<\/p>\n Used systems often carry evidence of their previous cell. Additional wiring, removed peripherals, altered connectors, legacy field interfaces, and undocumented changes may be harmless, useful, or problematic. The inspection must determine which is which.<\/p>\n Improvised electrical changes are especially important because they can complicate troubleshooting. A buyer should know whether the delivered configuration is understood well enough to support commissioning, recovery, and future maintenance.<\/p>\n If the controller must connect to existing PLC, safety, software, or production systems, compatibility becomes a separate engineering decision. URT\u2019s article on evaluating refurbished robot compatibility with existing systems<\/a> covers this risk in more depth.<\/p>\n A power-up test is necessary, but \u201cit turns on\u201d is a very low acceptance threshold. The objective is to observe startup behavior, identify active or recurring faults, confirm that essential supplied components communicate, and determine whether the system behaves consistently.<\/p>\n Record alarms rather than clearing them reflexively. An alarm may be minor, configuration-related, linked to removed cell equipment, or evidence of a more significant issue. Its meaning should be established using the correct manufacturer information and competent technical interpretation.<\/p>\n Repeated faults deserve particular attention. A system that can be reset for a demonstration may still have an unresolved condition that returns during movement, warm operation, communication, or production integration.<\/p>\n A seller demonstration can create a false sense of completeness if temporary equipment, external devices, or seller-owned components are being used to make the robot run. Confirm which hardware, software, cables, and peripherals are included in the transaction.<\/p>\n This distinction matters because the purchase price of the arm and controller is only one part of the project. Missing components may affect commissioning cost, schedule, and technical feasibility.<\/p>\n A robot that jogs a few degrees on each axis has demonstrated movement, not production readiness. Motion testing should be broad enough to expose behavior that may not appear in a short static demonstration.<\/p>\n Where safe and technically appropriate, qualified personnel should observe controlled axis movement through relevant portions of the operating range. The purpose is to identify abnormal noise, vibration, hesitation, inconsistent motion, unexpected fault behavior, or conditions that appear only in certain positions or directions.<\/p>\n Testing should also consider temperature and duration. Some problems are not obvious immediately after startup. A brief demonstration can miss behavior that develops after repeated movement or a longer operating period.<\/p>\n No-load movement can be useful, but it does not reproduce the intended application. Tooling changes mechanical demand, cable behavior, access, collision exposure, and the usable working envelope. Production performance also depends on fixtures, part presentation, sensors, safety logic, upstream flow, and downstream equipment.<\/p>\n This is why the inspection result should never be \u201cthe robot moved, therefore the cell will work.\u201d Robot capability and cell performance are different questions.<\/p>\n A technically healthy robot can still be the wrong purchase. Once condition has been assessed, the buyer must test the equipment against the real production requirement.<\/p>\n Start with the process. Define the part, tooling concept, required positions, orientation, cycle expectations, fixture arrangement, surrounding equipment, safety concept, and communication requirements. Only then can the robot be evaluated as part of a cell.<\/p>\n This is where many low-price purchases become expensive. The robot may require more integration work than expected, the controller may not fit the plant architecture, the working envelope may create access problems, or the intended tooling may reduce the practical margin available for the task.<\/p>\n Do not use specifications from a similar model, a base model, a reseller database, or memory. Final payload, reach, repeatability, controller, mounting, and tooling decisions should be checked against official manufacturer information for the exact model variant.<\/p>\n If exact variant data cannot be verified, delay detailed cell assumptions rather than filling the gap with numbers from a related robot. This is particularly important before fixture layout, end-of-arm tooling design, safety-envelope decisions, or cycle simulation.<\/p>\n Plants that are still deciding whether the process itself is a good automation candidate should first consider how to choose which process to robotize first<\/a>. A good robot cannot compensate for a poorly selected or unstable automation project.<\/p>\n The final step is not assigning the robot a simple pass or fail. It is converting findings into a purchase decision that reflects the complete project.<\/p>\n Separate findings into categories: confirmed acceptable condition, issues requiring repair, unknowns requiring verification, missing equipment, compatibility work, and application-specific integration requirements. This prevents a low purchase price from hiding costs that will appear later.<\/p>\n A robot with a higher initial price may be the lower-risk option if its identity, condition, controller configuration, documentation, and compatibility are clearer. Conversely, a cheaper robot can remain a sensible purchase when the buyer understands the required work and has the technical capability to complete it.<\/p>\n URT\u2019s analysis of the true total cost of ownership of a used robot versus a new robot<\/a> is relevant at this stage because inspection findings only become useful when they are translated into project cost and downtime exposure.<\/p>\n This checklist is best used after the physical and operational inspection. Mark unresolved items as unknown rather than assuming they will be easy to solve after purchase.<\/p>\n A checklist does not replace technical judgment. Its value is that it prevents a successful demonstration, clean appearance, or attractive price from dominating the decision before the important unknowns have been addressed.<\/p>\n There are situations where the correct inspection outcome is to delay the purchase. One is when the exact equipment identity remains unclear. Without confidence in the model and controller configuration, detailed engineering can rest on the wrong assumptions.<\/p>\n Another is when significant abnormal behavior appears during testing and the cause has not been established. The buyer does not need to reject every machine with a repair requirement, but the repair scope and commercial consequence should be understood before the transaction.<\/p>\n Purchase should also be delayed when compatibility is treated as an afterthought. If the plant has not assessed the intended tooling, cell layout, safety architecture, controller interfaces, software requirements, and support capability, mechanical condition alone is not enough to justify the investment.<\/p>\n Finally, a used robot may be the wrong choice when production risk is unusually sensitive to downtime and the organization lacks the spare parts strategy, internal capability, or external support needed for the selected platform. In that situation, another used unit, a refurbished option, or new equipment may represent the more defensible decision.<\/p>\n Confirm the exact robot and controller identity before making assumptions about condition or suitability. The model variant, controller generation, supplied hardware, and available documentation affect later decisions about compatibility, tooling, layout, support, and integration.<\/p>\n No. Power-up only confirms a limited part of the system state. A meaningful assessment also considers fault behavior, mechanical condition, controlled motion, controller and pendant condition, cables, documentation, compatibility, and the intended production application.<\/p>\n Controlled motion testing is an important part of the assessment because some abnormal behavior may appear only in particular positions or directions. Testing should be performed safely by competent personnel using procedures appropriate to the equipment.<\/p>\n Previous application information can help the inspector understand likely exposure to contamination, repeated motion patterns, process equipment, impacts, and other operating conditions. It does not prove current condition, but it can guide a more focused inspection.<\/p>\n Yes. Cosmetic condition does not establish mechanical health, controller compatibility, software availability, documentation quality, spare parts implications, or suitability for the intended cell. Appearance is one observation, not a complete condition assessment.<\/p>\n Missing records create uncertainty rather than automatic proof that the robot is defective. The buyer should document the information gap, increase the depth of technical verification where appropriate, and reflect the remaining uncertainty in the purchase decision.<\/p>\n The controller affects integration with the wider production system, including communication, software environment, peripheral equipment, safety architecture, support, and recovery. A mechanically sound arm can still create substantial project cost if the controller does not fit the intended cell.<\/p>\n No. Purchase price should be considered together with inspection findings, repairs, missing equipment, integration work, controller compatibility, spare parts, commissioning, training, and downtime exposure. The lower-priced machine can become the more expensive project if these costs are ignored.<\/p>\n If you are evaluating second-hand robot inspection, contact URT<\/a>. We will give you a direct, technical answer based on your actual production requirements.<\/p>\n","protected":false},"excerpt":{"rendered":"What to establish at this stage?<\/h3>\n
\n
\nStep 2: Review History and Documentation Before the Physical Test<\/h2>\n
Documentation worth requesting?<\/h3>\n
\n
\nStep 3: Inspect the Robot Mechanically Before Running It<\/h2>\n
Check each axis for abnormal mechanical behavior?<\/h3>\n
Inspect the wrist and tooling interface carefully?<\/h3>\n
\nStep 4: Inspect the Controller, Pendant, Cables, and Connections<\/h2>\n
Do not ignore modifications?<\/h3>\n
\nStep 5: Power Up the Robot and Review Fault Behavior<\/h2>\n
Check what is actually included in the working configuration?<\/h3>\n
\nStep 6: Test Motion Across a Meaningful Operating Range<\/h2>\n
Why a no-load test is not enough?<\/h3>\n
\nStep 7: Evaluate Compatibility With the Intended Application<\/h2>\n
Verify specifications before cell design?<\/h3>\n
\nStep 8: Convert Inspection Findings Into a Total Project Risk Decision<\/h2>\n
Use the final checklist as a decision gate?<\/h3>\n
\n
\nWhen a Second-Hand Robot Should Not Be Purchased Yet<\/h2>\n
\nFAQ<\/h2>\n
What is the first thing to check when inspecting a second-hand robot?<\/h3>\n
Is a successful power-up test enough to prove that a used robot is in good condition?<\/h3>\n
Should every axis be tested before buying a second-hand robot?<\/h3>\n
How important is the previous application of a used robot?<\/h3>\n
Can a clean-looking robot still be a risky purchase?<\/h3>\n
What if the seller cannot provide maintenance records?<\/h3>\n
Why is controller compatibility important when buying a second-hand robot?<\/h3>\n
Is the cheapest second-hand robot usually the best value?<\/h3>\n
\nTalk to URT About Second-Hand Robot Inspection<\/h2>\n