Pricing
00
In productionProbeginnerAI-assisted debugging

The AI blames the wrong tf frame

Use the evidence to fix the transform timeout the LLM mis-diagnosed.

Pairs with Debugging ROS with AI in the loop in Use AI efficiently with ROS 2. Read the concept first, then diagnose it here.

Unlock this lab with Pro

Operator report

tf lookups fail with 'extrapolation into the past'; the AI first blamed the frame names.

Ubuntu 24.04, ROS 2 Jazzy, rclpy/rclcpp, an LLM coding assistant + MCP

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01broadcaster rate→
  2. 02tf buffer→
  3. 03lookupOUT
02

How this lab works

You diagnose it. No command list.

Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you - finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.

03

Verification

Pass more than the visible symptom.

4 checks
  • Broadcast rate raised
  • Lookups succeed
  • Hidden regression behavior
  • Root cause explanation