Skip to content

Bolt X / Motoman Not Communicating With Flair — Axis Encoder Unplugged

Summary

A new Bolt X booted and loaded properly, and could be engaged with the lights coming on, but the rig model in Flair did not match the physical robot and the arm could not be controlled — after roughly 10 seconds Flair reported the robot had tripped, even though the robot itself stayed physically engaged. InTime showed "Motoman has stopped talking." The eventual cause was one of the arm's axis encoders (axis #3) had become physically unplugged, so Yaskawa had no positional data for that axis. Resetting that axis's home position via the teach pendant, then restarting the robot, restored communication. This is a distinct root cause from power-loss major-alarm re-zero — no power interruption was involved here, and the fix path (encoder reseat + single-axis pendant zero) is different.

Symptoms

  • Flair boots and loads the job normally; the robot can be engaged and lights come on.
  • The 3D rig model in Flair does not match the physical robot's actual position.
  • The arm cannot be controlled/moved from Flair.
  • After roughly 10 seconds, Flair reports the robot has tripped — but the physical robot remains engaged (motors stay on).
  • InTime console reports "Motoman has stopped talking" after the trip.
  • E-stop can still be enabled and the robot engaged with the pendant — the robot hardware itself checks out fine in isolation.
  • Different Ethernet cables/ports on the hub don't change the behavior.

Community Guidance

[RESOLVED] Motoman "Native All-Zero" Position Means Flair Isn't Talking to the Robot Yet

Community — Timothy Heys Cerchio — 12 June 2026

"This is Motoman 'native' all zero position. Means Flair is not really talking to Motoman, yet."

This confirms the symptom is a communication failure between Flair/InTime and the Motoman (Yaskawa) controller, not a mechanical or software-config issue on the Flair side. Because Track on Bolt X is also driven through Motoman (as Robot Axis 7), a Track trip will take the rest of the robot down with it.

confidence_score: 0.8

[RESOLVED] Checklist Before Opening the Base

Community — Timothy Heys Cerchio, Simon Wakley — 12 June 2026

Before opening the robot base, confirm:

  1. The Pinch Wheel is in place with the Datum/Limit cable connected.
  2. A full power cycle of the whole Bolt X has actually been done (not just a Flair restart) — LEDs on the side of the controller indicate when the robot is ready to talk; give it a couple of minutes to boot.
  3. If the motors visibly engage but the rig model still doesn't look right, this points to a real-time feedback problem rather than a full communication failure — still requires a full power cycle of the Bolt X.

Simon Wakley: "If it engages but does not look right you will need to power cycle and start again... If the motors engage then obviously you ARE talking to the robot but the real-time feedback is no[t] working. So full power cycle of BoltX is required."

confidence_score: 0.78

[RESOLVED] Root Cause Found — Unplugged Axis-3 Encoder

Community — 13 June 2026

"We found the solution! For anyone curious, one of the axes encoders got unplugged which resulted in yaskawa not having any positional data for the arm axis (axis #3). Once we reset that home position on the robot through the pendant (following QSG instructions for how to re-zero arm if encoder batteries fail) and restarting the robot flair was able to communicate and fully move the arm around."

Steps:

  1. If the checklist above doesn't resolve it, open the base and check each axis's encoder connector for a loose or fully disconnected plug — axis 3 was the culprit in this case, but check all axes.
  2. Reseat the connector.
  3. Reset that axis's home/zero position via the teach pendant, following the same encoder-battery-failure re-zero procedure in the Bolt X QSG (the connector loss has the same effect on positional data as a dead encoder battery would).
  4. Restart the robot fully. Flair should then communicate and the arm should move correctly.

Note from the field: the large plug on the servo pack carries all 6 axes' wiring, power, and encoders together, while the 2 smaller plugs handle the external track axis (power and encoder separately) — check the plug type against which axis is affected before assuming which connector to inspect.

confidence_score: 0.85

Official Documentation