Skip to main content

Section 8.1 Introduction to Multi-Agent Systems and Communication Paradigms

Up to this point, we have treated our robot as a solitary agent working alone in its environment. However, many real-world challengesβ€”such as searching a vast disaster area, managing an automated warehouse, or harvesting an entire agricultural fieldβ€”are far too large or complex for a single robot to complete efficiently.
A Multi-Agent System (MAS) consists of multiple autonomous robots (agents) that interact, coordinate, and share tasks to achieve individual or collective goals.
Picture two different ways to organize a fleet of robots. In a Centralized Architecture, a single Central Controller sits above every agent, sending commands down to Agent A, Agent B, and Agent C individually. In a Decentralized Architecture, there is no central controller at all: Agent A talks directly to Agent B, and Agent C talks directly to Agent D, each pair coordinating peer-to-peer.
Figure 8.1.1. Centralized coordination routes commands through one controller, while decentralized coordination relies on direct communication among peer agents.

Subsection 8.1.1 Coordination Architectures: Centralized vs. Decentralized

When designing multi-robot systems, roboticists choose between two primary control architectures:
  1. Centralized Systems: A single master computer collects data from every robot, computes all decisions, and sends back movement commands.
    • Pros: Optimal task allocation and globally efficient paths.
    • Cons: Single point of failure (if the central server crashes, the whole fleet stops); heavy network bandwidth bottlenecks.
  2. Decentralized (Distributed) Systems: Each robot runs its own decision-making logic locally based on local sensor data and short-range messages from neighboring peers.
    • Pros: Scalable to thousands of robots; highly robust to individual agent failures.
    • Cons: Sub-optimal global decisions; potential for local conflicts.

Subsection 8.1.2 Real-World & VEX Robotics Examples

  • Real-World Example (Amazon Fulfillment Warehouses): Hundreds of Kiva drive units move packages across factory floors. A central cloud server assigns tasks and calculates collision-free intersection schedules (Centralized Control). However, if an unexpected obstacle appears, individual drive units use local proximity sensors to stop instantly without waiting for server confirmation (Decentralized Safety Override).
  • VEX Robotics Example (VEX V5 VEXnet Communication): In VEX AI competitions or multi-robot cooperative labs, VEX V5 Robot Brains communicate wirelessly using VEXnet or custom peer-to-peer radio protocols. Robots share field telemetryβ€”such as target positions or current locationsβ€”so one robot can collect game elements while its teammate blocks opponent pathways.

Subsection 8.1.3 Section 8.1 Interactive Exercises

Subsubsection 8.1.3.1 Exercise 8.1.2: CodeLens Trace β€” Peer-to-Peer Message Handling

Step through the execution below to observe how a robot agent updates its local knowledge table based on incoming peer messages.

Reading Questions 8.1.4 Reading Questions

Check your understanding

1. Exercise 8.1.1: Control Architectures Conceptual Check.

Why might an engineering team choose a decentralized control architecture over a centralized server when deploying a fleet of 500 search-and-rescue drones?
  • Centralized systems scale better to thousands of agents because there is no network traffic.
  • Incorrect. Centralized systems experience severe bandwidth bottlenecks as agent counts grow.
  • Decentralized systems prevent a single point of failure and scale better across large robot fleets.
  • Correct! Decentralized systems lack a single point of failure; if one drone breaks or loses connection, the rest of the fleet continues operating.
  • Decentralized systems guarantee optimal global path routes for all agents.
  • Incorrect. Decentralized systems make local choices that may be sub-optimal globally.
  • Centralized systems do not require any communication infrastructure.
  • Incorrect. Centralized systems depend entirely on continuous communication infrastructure.
You have attempted of activities on this page.