A Robot Makes an Unusual Sound: What to Record for Service

An unfamiliar sound or vibration from a robot is a symptom worth recording, not a diagnosis of a particular joint or gearbox. A useful service request describes when the behavior occurs, what changed and what the operator observed. The service provider can then decide which inspections and tests are appropriate for the actual robot and its installation.

Describe the sound without naming a cause

Record whether the observation is a new sound, a change in an existing sound or a vibration felt in nearby equipment. Note the date, time, robot and controller identifiers and the task underway. If the sound appears during a particular movement or after a period of operation, describe that pattern. Avoid statements such as a failed gearbox unless a qualified inspection has established the cause.

If the equipment presents an immediate hazard or has stopped unexpectedly, follow the site's stop and escalation procedures. Do not keep running a potentially unsafe machine merely to obtain a clearer recording. A technician can determine whether and how a controlled demonstration is appropriate.

Document the complete installation

A sound heard near the arm may also involve the tool, fixture, mounting structure or nearby machinery. Record the installed gripper, payload, mounting arrangement and other equipment operating at the time. Identify whether the sound is observed with a particular workpiece or during a particular step, without assuming that the workpiece caused it.

Universal Robots' deployment guidance discusses the importance of a sufficiently rigid mounting surface that does not introduce vibration into the application. This is one manufacturer-specific consideration, not a diagnosis for every vibrating robot. The responsible service provider should review the relevant model, installation and site conditions.

Preserve the change history

Ask what changed before the observation: a tool replacement, new part, modified program, relocation, repair or change in surrounding equipment. Record the date and the person who supplied the information. If a new sound appeared after a change, that timing is a reason to investigate the change, not proof that it caused the problem.

Keep the previous and current program or configuration identifiers where the organization has them. Do not alter settings or replace components before documenting the existing state, unless the site's emergency procedures require immediate action. The service team needs to understand what was in use when the symptom occurred.

If the issue appears only on one shift or with one product, record those observations separately. Differences in production schedule, tooling and nearby machinery can help the service team frame its questions. Avoid asking an operator to repeat an unsafe condition to prove that the pattern exists; the available records and a planned inspection are the appropriate starting point.

Collect evidence within the site's procedures

A dated recording, operator note and relevant controller messages may help a technician understand the sequence. Record where the person was standing and what other equipment was running, because a recording can capture sounds from several sources. Keep the original file and avoid editing it in a way that removes timing or context.

Universal Robots' inspection and maintenance plan lists checks for the arm and control box and advises contacting a service provider if a fan sounds abnormal. It illustrates why the source of a sound matters. Use the manual for the actual equipment and do not open a control box or perform maintenance without the required qualification and authorization.

Agree on the scope of a service visit

Provide the service provider with the observation, equipment identifiers, recent changes, maintenance history and any relevant log files collected through approved procedures. Ask which further information is needed and whether an on-site visit is required. Support files and recordings may contain business information; share them only with authorized recipients.

Before any test, agree who controls the work area, which equipment will be operating and what safeguards are required. The service provider should explain the test's scope and record any limitation. A test performed without the usual tool or load may help isolate a condition, but it does not reproduce every aspect of the production task.

Close the record with findings, not assumptions

After inspection, record what was checked, what was found, any repair or adjustment, and who approved the return to operation. If the technician could not reproduce the sound, retain the original evidence and state that the cause remains unresolved. A quiet result during a short test is not proof that no intermittent condition exists.

For another service intake topic, read our guide to documenting an error message and browse the robot service archive. A clear symptom history makes the next investigation more useful without turning an observation into an unsupported repair claim.