What the C160 alarm means

The robot was powered off last time without a clean stop (e.g. E-stop or power cut), so the measured joint positions may not match the stored ones; the controller refuses to trust the position until verified. This is one of the faults our repair team handles on Universal Robots CB3 / e-Series (UR5/UR10/UR16/UR20) systems — the cause is usually identifiable within the first on-site inspection.

Most common causes

  • Power cut or emergency stop while the robot was moving
  • Encoder count lost during abrupt stop
  • Battery-backed encoder data corrupted
  • Brake released while unpowered and arm moved
Field note: the first item on this list is what we find most often on real machines. Check it before you go deeper.

Step-by-step field fix

  1. Verify in the 3D view that the displayed position matches the real robot
  2. Stand clear, then run the first program cycle slowly to observe behavior
  3. If positions clearly disagree, move joints to calibration marks and re-calibrate
  4. Check the encoder battery and connectors
  5. Avoid powering off mid-motion; use proper stop routines
Safety first: never bypass safety circuits or force contactors closed. If the alarm involves E-stop chains, brakes or drive power, and you are not a trained robot technician, contact a professional — wrong moves here can cost you a robot or an injury.

Still stuck? Get an engineer on the phone — right now

Tell us the alarm code, the robot model and what was happening when the alarm came up. Our engineers run these diagnostics every day, and remote diagnosis by phone or video call is free.

Get a Free Remote Diagnosis See Repair Services

Hotline: +86-20-39029800 · WhatsApp: +86-188-1886-2860

Related System & Program alarms

C71A1 — Joint Firmware Mismatch (Size 1 Joint)
Other brands: we also keep field-fix libraries for Kawasaki · Staubli · Epson and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the Universal Robots C160 alarm mean?

The robot was powered off last time without a clean stop (e.g. E-stop or power cut), so the measured joint positions may not match the stored ones; the controller refuses to trust the position until verified. In field practice it belongs to the system & program family of faults.

QCan I clear a Universal Robots C160 alarm myself?

Sometimes. Work through the step-by-step checks on this page — the first listed cause is what we find most often in the field. If the alarm returns after two attempts, or the fault involves power, brakes or safety circuits, stop and call a qualified robot service engineer.

QHow fast can a Henghuan engineer help?

On-site response in the Pearl River Delta within 30 minutes to 3 hours, across mainland China in 1-3 business days, and worldwide within 2-5 business days. Remote diagnosis by phone/WhatsApp/video is available immediately.

Written by the Henghuan Robotics repair team from field service experience. Alarm descriptions are our own summary for troubleshooting reference and may vary by controller and software version — when in doubt, check your Universal Robots documentation or contact us. Henghuan is an independent service provider, not affiliated with or endorsed by Universal Robots.