Add FMS network documentation summary pages #3149
Open
+614
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds three new documentation pages summarizing key information from the FMS whitepaper: - fms-network-architecture.rst: Explains FMS network topology, VLANs, IP addressing, wireless specs, and security - fms-ports-protocols.rst: Reference table of network ports and protocols used by FMS and FRC software - network-performance-optimization.rst: Practical guidance for staying within 7 Mbps bandwidth limit These pages provide teams with essential FMS networking information without duplicating the full technical details from the FMS whitepaper. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
rzblue
requested changes
Oct 13, 2025
| The FMS network is an Ethernet-based system that connects all robots, driver stations, and field equipment. The network centers around a **Score Switch** that manages traffic between: | ||
|
|
||
| - **Field Router**: Connects to the FMS server and manages alliance networks | ||
| - **FMS Server**: Controls match flow and communicates with all robots |
There was a problem hiding this comment.
Suggested change
| - **FMS Server**: Controls match flow and communicates with all robots | |
| - **FMS Server**: Controls match flow and communicates with Driver Station software. |
|
|
||
| - **Field Router**: Connects to the FMS server and manages alliance networks | ||
| - **FMS Server**: Controls match flow and communicates with all robots | ||
| - **Field Access Points (APs)**: Provide 6 GHz wireless connectivity to robots |
There was a problem hiding this comment.
Suggested change
| - **Field Access Points (APs)**: Provide 6 GHz wireless connectivity to robots | |
| - **Field Access Point (AP)**: Provide 6 GHz wireless connectivity to robots |
| - **Field Access Points (APs)**: Provide 6 GHz wireless connectivity to robots | ||
| - **Smart Router**: Manages external connectivity and network services | ||
|
|
||
| All competition field communication uses dedicated wireless access points operating in the 6 GHz band with 802.11ax (Wi-Fi 6E) to minimize interference from spectator devices. |
There was a problem hiding this comment.
Only communication between robots and the rest of the network uses wireless, and there's only 1 AP.
| - **Frequency Band**: 6 GHz exclusively (avoids 2.4/5 GHz congestion from phones, tablets) | ||
| - **Standard**: 802.11ax (Wi-Fi 6E) | ||
| - **Encryption**: WPA3 with AES encryption | ||
| - **Security Keys**: Unique per team, per event (teams receive keys at check-in) |
There was a problem hiding this comment.
teams program the radio using a kiosk, they don't get the keys directly
Comment on lines
53
to
71
| ## Wireless Specifications | ||
|
|
||
| FMS wireless uses modern standards to ensure reliable connectivity: | ||
|
|
||
| - **Frequency Band**: 6 GHz exclusively (avoids 2.4/5 GHz congestion from phones, tablets) | ||
| - **Standard**: 802.11ax (Wi-Fi 6E) | ||
| - **Encryption**: WPA3 with AES encryption | ||
| - **Security Keys**: Unique per team, per event (teams receive keys at check-in) | ||
|
|
||
| .. warning:: Field staff devices use separate 2.4 GHz and 5 GHz networks. Robot radios must be configured for 6 GHz operation at competition. | ||
|
|
||
| ## Security Features | ||
|
|
||
| FMS implements multiple security layers: | ||
|
|
||
| 1. **VLAN Isolation**: Teams cannot see or communicate with other teams' networks | ||
| 2. **WPA3 Encryption**: All wireless traffic is encrypted with per-team keys | ||
| 3. **Port Restrictions**: Only approved network ports are allowed (see :doc:`fms-ports-protocols`) | ||
| 4. **Traffic Inspection**: FMS monitors network traffic for rules compliance |
There was a problem hiding this comment.
This whole section feels a bit... advertisey?
| - roboRIO: ``10.TE.AM.2`` (DHCP from robot radio) | ||
| - Other robot devices: ``10.TE.AM.200`` - ``10.TE.AM.219`` (DHCP from robot radio) | ||
|
|
||
| .. note:: The Field Router does **not** provide DHCP services to robot devices. Your team's robot radio provides DHCP addressing for the robot network. |
There was a problem hiding this comment.
Suggested change
| .. note:: The Field Router does **not** provide DHCP services to robot devices. Your team's robot radio provides DHCP addressing for the robot network. | |
| .. note:: The Field Router does **not** provide DHCP services to robot devices. Your team's robot radio provides DHCP addressing for devices onboard the robot. |
| 1. **Driver Station** connects to field via Ethernet or field AP, receives DHCP address from FMS | ||
| 2. **Robot Radio** connects to 6 GHz field AP using team-specific WPA3 key | ||
| 3. **roboRIO** receives DHCP address ``10.TE.AM.2`` from robot radio | ||
| 4. **FMS Server** establishes control connection with both DS and robot |
There was a problem hiding this comment.
Suggested change
| 4. **FMS Server** establishes control connection with both DS and robot | |
| 4. **FMS Server** establishes connection with the Driver Station software and begins sending control packets to the Driver Station software. |
| 2. **Robot Radio** connects to 6 GHz field AP using team-specific WPA3 key | ||
| 3. **roboRIO** receives DHCP address ``10.TE.AM.2`` from robot radio | ||
| 4. **FMS Server** establishes control connection with both DS and robot | ||
| 5. **Driver Station** sends control packets through FMS to robot |
There was a problem hiding this comment.
Suggested change
| 5. **Driver Station** sends control packets through FMS to robot | |
| 5. **Driver Station** sends control packets to the robot, corresponding to the FMS-commanded mode |
| 3. **roboRIO** receives DHCP address ``10.TE.AM.2`` from robot radio | ||
| 4. **FMS Server** establishes control connection with both DS and robot | ||
| 5. **Driver Station** sends control packets through FMS to robot | ||
| 6. **Robot** sends status information back through FMS to DS |
There was a problem hiding this comment.
Suggested change
| 6. **Robot** sends status information back through FMS to DS | |
| 6. **Robot** sends status information back to the Driver Station | |
| 7. **Driver Station** sends status information back to the FMS |
| 5. **Driver Station** sends control packets through FMS to robot | ||
| 6. **Robot** sends status information back through FMS to DS | ||
|
|
||
| All control traffic is routed through the FMS server, which enforces match timing, enable/disable states, and mode selection (auto/teleop/test). |
Key changes: - Clarified FMS Server communicates with Driver Station software, not robots directly - Changed "Field Access Points" to singular "Field Access Point" - Simplified VLAN section to focus on isolation rather than specific VLAN numbers - Updated wireless section to clarify only robot communication uses the 6 GHz AP - Changed WPA3 key distribution to mention teams use event kiosks to configure radios - Removed "advertisey" language and incorrect traffic monitoring claims from security section - Rewrote communication flow using "conductor" analogy: FMS tells DS what to do, but DS communicates directly with robot - Corrected communication flow steps to reflect DS-robot direct communication with FMS coordinating - Updated field firewall description to clarify it restricts ports, doesn't monitor/control all traffic - Improved field vs pits section to be more practical and accurate All changes verified against FMS whitepaper for technical accuracy. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds three new documentation pages summarizing key information from the FMS whitepaper to help teams understand FMS networking:
fms-network-architecture.rst: Explains how FMS network is structured
fms-ports-protocols.rst: Reference for network ports and protocols
network-performance-optimization.rst: Practical bandwidth optimization guidance
Design Decisions
Testing
🤖 Generated with Claude Code