Bridging commercial Android hardware to a deterministic robotics bus requires
a strict, tiered architecture. The phones excel at heavy compute, ML routing,
and mesh networking, but lack the native hardware interfaces and real-time
operating system (RTOS) capabilities to drive motors directly.
Here is the top-level N+1 hardware and communication hierarchy:
Layer 1: The Orchestration Cluster (The Brains)
 * Hardware: N+1 Android phones connected to a ruggedized USB-C Gigabit
Ethernet Switch mounted inside the torso.
 * Inter-Node Comms: The phones form an isolated, hardwired local IP subnet.
They communicate using UDP multicast for high-frequency sensor telemetry
sharing and TCP for strict state-machine synchronization and leader election.
 * Redundancy Logic: All phones continuously ingest the same event streams
from the lower layers. If the active leader phone stops broadcasting its
high-frequency heartbeat over the IP mesh, a standby phone immediately binds
to the outgoing port and takes over orchestration.
Layer 2: The Spinal Bridge (Protocol Translation)
 * Hardware: A dedicated bridge microcontroller board (e.g., an STM32H7 or a
cluster of RP2040s) connected to the Ethernet switch (via an SPI-to-Ethernet
chip) or directly to the active phone via USB-C (using USB CDC Virtual
Serial).
 * Function: The bridge isolates the non-deterministic Android OS from the
real-time robotics bus. It acts purely as a high-speed translatorpulling
serialized payloads (like FlatBuffers or Protobuf) from the phones, segmenting
them into strict CAN FD frames, and injecting them into the bus via lock-free
ring buffers.
Layer 3: The Transport Bus (The Nervous System)
 * Hardware: Dual, physically isolated twisted-pair cables (Bus A and Bus B)
running from the torso to every socket, driven by CAN FD transceivers (e.g.,
TCAN4550).
 * Topology: Multidrop bus architecture. CAN FD provides up to 8 Mbps
throughput and hardware-level packet collision arbitration. It operates as a
publish-subscribe broadcast networkmessages are tagged by event type, not
destination addresses.
Layer 4: Socket Controllers (The Muscles)
 * Hardware: RP2040 microcontrollers housed at each modular joint socket,
equipped with dual CAN transceivers (tapping into both Bus A and Bus B
simultaneously) and motor driver ICs.
 * Function: These edge nodes handle the microsecond-level physics. They
subscribe to target commands ("set wheel velocity to X"), run the local PID
control loops to achieve that target, and continuously broadcast their
telemetry (encoder position, current draw, voltage) back up the bus to be
ingested by the Android cluster.