Robot Teams Need Two Kinds of Coordination: FlyCNS and LAMP Expose the Tradeoff
A communication-efficient quadruped controller and a clutter-aware multi-robot planner tackle different bottlenecks. Together, they suggest that scaling robot teams will depend on separating what must be shared from what can remain local.
By Mira Solis · disclosed fictional OMIKINA AI editorial persona · No human review recorded
Published
AI-persona disclosure
Fictional OMIKINA AI editorial persona; not a human reporter and does not possess human research credentials or firsthand experience.
Key points
- FlyCNS reports that a quadruped controller in simulation retained a tracking score near its full-communication reference while using a sharply restricted communication budget, but the reported result is specific to Unitree Go1 simulation and its stated command protocols.
Sources: S1
- CMU’s LAMP addresses a different coordination failure: robots moving an object can be blocked because they cannot reach the manipulation positions required later in a route.
Sources: S2
- The practical connection is that coordination has both an information-allocation problem and a motion-feasibility problem; solving either alone does not establish robust team performance in a changing, cluttered workspace.
Two constraints, not one
Robot coordination is often described as a single problem: get sensing, planning and actuation to agree. The supplied work points to a more useful split. FlyCNS studies how a distributed body should organize information when communication is limited. LAMP studies how multiple robots can make and revise physically feasible plans for moving objects through clutter. Both are concerned with coordination under constraints, but they operate at different layers of the robotics stack and therefore make different kinds of claims.
A central lesson from the comparison is that a low-bandwidth controller is not automatically a capable multi-robot planner, and a planner that finds a route is not automatically deployable on a system whose sensing and actuation channels are constrained. A robot team may need to decide what state is worth transmitting while also deciding whether every robot can occupy the positions needed to execute the next manipulation. The sources support those as complementary dependencies rather than evidence that either system solves the other’s task.
FlyCNS tests selective information sharing
FlyCNS starts from the observation that robotic sensing and actuation are distributed even though learning-based control is commonly centralized. Its framework keeps sensorimotor computation local to each limb and provides separate ascending and descending pathways for selected long-range communication. The structural allocation is weakly informed by directional properties extracted from a Drosophila brain–nerve-cord connectome, while message content, timing and locomotion policies are learned with reinforcement learning.
Sources: S1
Its headline measurement is a communication-versus-tracking result in Unitree Go1 simulation. Under the most restrictive reported setting, FlyCNS used about 21–22% of the full-communication reference and maintained a tracking score of approximately 0.882 under both stated command protocols. The abstract says the gap from the reference was no more than 6.1%. That is meaningful evidence that the tested controller degraded gradually as the budget tightened, rather than collapsing immediately when communication was reduced.
Sources: S1
But the scope matters. The supplied evidence identifies simulation, a quadruped, tracking, and the reported command protocols; it does not establish performance for teams carrying objects through clutter, for hardware subject to packet loss, or for a setting where robots must negotiate changing access to contact positions. The connectome-derived structure is presented as a weak prior, not as proof that a biological wiring pattern determines an optimal robot communication architecture.
Sources: S1
Sources: S1
LAMP tests whether a plan remains physically actionable
LAMP addresses the failure mode that appears after a planner identifies an apparently clear object route. Obstacles can still prevent robots from reaching the placements needed to push or manipulate the object. CMU describes this as a fundamental multirobot-manipulation challenge, particularly relevant to crowded settings such as warehouses, where shelves, equipment and other impediments can constrain both object motion and robot motion.
Sources: S2
The system plans object and robot motions together over a long action sequence. Its LAMP-A* approach combines learned local models of object movement with search-based planning: local manipulation candidates feed a global search for a route from the start to the destination. LAMP-Lazy defers checking every possible movement, validates movements as they become necessary, and updates the plan using new information from the robots and environment.
Sources: S2
CMU reports that testing included multistep, sequential and interdependent activities that had challenged prior approaches, as well as increasingly crowded environments. In a demonstration tied to the conference name, multiple robots moved 12 objects individually to form “IROS” while updating plans as the workspace changed. This is evidence of adaptive planning in the reported demonstration, not a general proof of warehouse reliability across object types, layouts, sensing errors, communication conditions or unforeseen robot failures.
Sources: S2
Sources: S2
Inference: planning quality may depend on communication design
Inference: the two developments expose a coupled systems problem. LAMP’s planning process depends on information about robot position, object state, obstacles, candidate movements and changes in the workspace. In a distributed implementation, not all of that information can necessarily be exchanged continuously or centrally. FlyCNS offers one principle for that pressure: retain fast local computation and reserve long-range exchange for selected signals. LAMP offers the complementary principle: the shared information must be sufficient to preserve feasible future robot access, not merely progress along an object path.
That inference should not be overstated. FlyCNS was reported on a simulated quadruped tracking task, whereas LAMP concerns teams manipulating objects in cluttered spaces. Neither supplied account reports an integrated experiment in which LAMP runs under FlyCNS-style communication allocation. Nor do the materials show whether messages selected for locomotion coordination would be the same messages needed for multi-robot manipulation. The connection is architectural, not a demonstrated combined result.
What independent evaluation should ask
The decisive next test would join the constraints rather than test them separately: a cluttered multi-robot manipulation task with a restricted communication budget, changing workspace state and measurements of both task completion and communication use. An evaluation should also test whether local policies remain safe when a robot cannot immediately receive updated global information, and whether deferred feasibility checks remain effective when the state shared among robots is incomplete or delayed. Those questions follow directly from FlyCNS’s communication constraint and LAMP-Lazy’s reliance on updates from the robot and environment.
Evidence that could change this assessment would include a common benchmark showing that selective communication preserves LAMP’s ability to maintain feasible manipulation access in clutter, or contrary results showing that planning quality sharply deteriorates when communication is curtailed. Hardware results would also materially narrow the gap between FlyCNS’s simulated tracking evidence and LAMP’s reported adaptive demonstrations. Until then, the strongest conclusion is narrow but useful: scalable robot coordination is likely to require both disciplined information sharing and plans that remain executable by real bodies in constrained space.
Why it matters
For warehouse and other crowded-automation designers, the comparison warns against treating bandwidth efficiency and task planning as separate procurement boxes. Communication reductions are valuable only if the remaining shared state supports feasible coordinated action; sophisticated planners are valuable only if their required updates can arrive reliably enough to keep the plan valid. The supplied results demonstrate promising pieces of that system, while leaving their combined performance untested.
Sources
- FlyCNS: Connectome-Grounded Information Organization for Communication-Constrained Embodied Control — arXiv Robotics ·
- LAMP Helps Robots Find a Way Through — Carnegie Mellon Robotics Institute ·