What the 1105 alarm means

The reported axis failed to reach its target position window within the configured monitoring time — the drive commanded motion but the axis did not follow. This is one of the faults our repair team handles on KUKA KRC2 / KRC4 / KRC5 (KSS) systems — the cause is usually identifiable within the first on-site inspection.

Most common causes

  • Wrong mechanical or gear-ratio parameters, or $IN_POS_MA / $TIME_POS windows set too tight
  • Damaged or leaking balancing system on axis 2/3
  • Motor or brake fault — brake not releasing
  • Encoder or motor cable connection fault
  • Mechanical obstruction or seized gearbox
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. Check for an obstruction or mechanical binding on the reported axis
  2. Verify the brake releases when drives are on (listen and measure)
  3. Inspect the motor-encoder cable and connectors
  4. For axis 2/3, check the balancing cylinder for damage or leakage
  5. Review $IN_POS_MA[] and $TIME_POS[] after any mechanical change; replace motor or gearbox if the axis still lags
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 Motion & Path alarms

1001 — Operator Safety Acknowledgment Required 1002 — Drives-On Not Asserted ($DRIVES_ON) 1004 — File System Error 1010 — Move Enable Missing — E-Stop or Safety Relay Open 1015 — No Program Selected 1020 — Pending Message Not Acknowledged ($CONF_MESS)
Other brands: we also keep field-fix libraries for ABB · Yaskawa · Universal Robots and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the KUKA 1105 alarm mean?

The reported axis failed to reach its target position window within the configured monitoring time — the drive commanded motion but the axis did not follow. In field practice it belongs to the motion & path family of faults.

QCan I clear a KUKA 1105 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 KUKA documentation or contact us. Henghuan is an independent service provider, not affiliated with or endorsed by KUKA.