Communications
Protocols, couriers, and sessions
Communications reference
Technical reference for OctoMY™'s communication system.
Did You Know?
OctoMY™ uses a custom UDP-based protocol instead of TCP because real-time robot control needs low latency more than guaranteed delivery. A dropped packet saying "turn left" is better handled by sending a new "turn left" than by waiting for retransmission of the old one. The protocol includes optional reliability for messages that do need guaranteed delivery.
Reference
| Topic | Description |
|---|---|
| Architecture | Layer architecture and key concepts |
| Discovery | Node discovery and peer detection |
| Protocols | Wire protocols and packet formats |
| Encryption | End-to-end encryption: handshake, session keys, AEAD |
| Couriers | Message routing system |
| Sessions | Session lifecycle and management |
| Acoustic Protocol | Acoustic communication: BanterClient, FSK codecs, chirp sync, DSP pipeline |
| BanterLab | Acoustic testing tool: parameter sweeps, auto-test, ablation specs |
| Source Files | Complete source file listing |
Overview
OctoMY™ uses a custom UDP-based protocol optimized for:
- Low latency real-time control
- NAT traversal
- Encrypted peer-to-peer communication
- Unreliable network resilience