Software Requirements Communication System

3.5 Communication System (Antenna)

3.5.1 Objectives

• Stable, low-latency, high-bandwidth Rover↔Base Station link.
• Redundancy/recovery for dropouts.
• Simultaneous video + telemetry + control without interference.
• Measurable metrics for optimization.

3.5.2 Functional Requirements

FR-5.1 Knowledge Transfer & Setup

• Preserve prior networking configs/manuals/procedures.
• Recreate and verify baseline setup before optimization.
• Include IP configs, topology diagrams, antenna placement guidelines.

FR-5.2 Testing & Benchmarking

• Use ping, iperf3, ROS network diagnostics.
• Measure latency/bandwidth/packet loss under realistic load (video + telemetry).
• Benchmark antenna orientations, 2.4/5 GHz, power levels.
• Log metrics for regression.

FR-5.3 Integration with Rover Software

• Configs (IP/ports/firewall) comply with ROS 1/2 comms.
• Support: one ZED2i stream + other camera feeds + telemetry with ≤ 1% packet loss.
• Auto-reconnect within ≤ 5 s after drops.
• UI shows latency, bandwidth utilization, signal strength.
• Modular configs in network_config.yaml.

3.5.3 Non-Functional Requirements

ID	Type	Requirement
NFR-5.1	Latency	Round-trip ≤ 300 ms (standard field).
NFR-5.2	Bandwidth	Sustained ≥ 50 Mbps (ZED2i + telemetry).
NFR-5.3	Reliability	Stable ≥ 30 minutes; ≤ 1% packet loss.
NFR-5.4	Recovery	Auto reconnection ≤ 5 s.
NFR-5.5	Maintainability	Configs and procedures documented and version-controlled.

3.5.4 Verification Criteria

• Baseline network reproduced and working.
• Round-trip latency < 300 ms with live video + telemetry.
• Throughput supports ZED2i + multiple cameras without drops.
• Packet loss < 1% over 30-minute field test.
• Forced disconnect → auto-reconnect ≤ 5 s.
• Field testing demonstrates stability across orientations/ranges.
• Procedures, IP configs, and benchmarks documented for future members.