A field management system that just works.
For the game-agnostic version, see Cheesy Arena Lite.
| Device | IP | Username | Password |
|---|---|---|---|
| Audience Display | 10.0.100.69 |
titansfms |
titansfms |
| FMS Access Pi | 10.0.100.TBD |
tbd | tbd |
The Cisco Catalyst 3850 runs ipbasek9 which does not support NAT. An Orange
Pi running Ubuntu is used as the NAT router so that all team VLANs have
internet access at the same time as robot communications.
- Orange Pi running Ubuntu with two NICs: built-in Ethernet (WAN) and a USB Ethernet dongle (LAN).
- A phone Ethernet hotspot or venue internet drop for the WAN connection.
[Phone hotspot / venue drop]
|
Orange Pi eth0 (WAN – DHCP client to hotspot/venue)
Orange Pi eth1 (LAN – USB dongle, static 10.0.100.10/24)
|
3850 Gi1/0/7 (access port, VLAN 100)
|
3850 VLAN 100 SVI (10.0.100.3/24, switch gateway)
|
All other VLANs (10/20/30/40/50/60/300) routed by the switch
| Device / Interface | IP | Notes |
|---|---|---|
| Orange Pi LAN (eth1) | 10.0.100.10/24 |
Static; NAT router LAN |
| Switch VLAN 100 SVI | 10.0.100.3/24 |
Switch L3 gateway |
| Switch default route | via 10.0.100.10 |
Internet next-hop = Orange Pi |
- Removed: all
ip nat inside/ip nat outsidecommands and theNAT-INSIDEACL (unsupported onipbasek9). - Removed:
ip address dhcponinterface Vlan200(WAN is now on the Pi). - Added:
ip route 0.0.0.0 0.0.0.0 10.0.100.10default route. - Updated:
GigabitEthernet1/0/7is now the dedicated Orange Pi LAN port (description OrangePi-NAT-LAN,spanning-tree portfast).
Replace eth0 / eth1 with the actual interface names shown by ip link.
1. Set a static LAN IP (netplan – persistent across reboots)
Create /etc/netplan/99-orangepi-lan.yaml:
network:
version: 2
ethernets:
eth1:
addresses:
- 10.0.100.10/24Apply:
sudo netplan apply2. Enable IPv4 forwarding (persistent)
echo 'net.ipv4.ip_forward=1' | sudo tee /etc/sysctl.d/99-ip-forward.conf
sudo sysctl -p /etc/sysctl.d/99-ip-forward.conf3. Configure NAT and forwarding rules
# NAT outbound traffic on WAN interface
sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
# Allow forwarding from LAN to WAN
sudo iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
# Allow return traffic from WAN back to LAN
sudo iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT4. Make iptables rules persistent
Install iptables-persistent and save:
sudo apt-get install -y iptables-persistent
sudo netfilter-persistent saveRules are automatically restored on boot by netfilter-persistent.
On the switch:
show ip route | include 0.0.0.0 ! should show default route via 10.0.100.10
ping 8.8.8.8 source vlan100 ! should succeed once Pi WAN is up
On the Orange Pi:
ip route # default route via hotspot on eth0
sudo iptables -t nat -S | grep MASQUERADE # NAT rule present
curl -s https://ifconfig.me # shows public WAN IPFor participants and spectators
- Same network isolation and security as the official FIRST FMS
- No-lag realtime scoring
- Team stack lights and seven-segment display are replaced by an LCD screen, which shows team info before the match and realtime scoring and timer during the match
- Smooth-scrolling rankings display
- Direct publishing of schedule, results, and rankings to The Blue Alliance
For scorekeepers and event staff
- Runs on Windows, macOS, and Linux
- No install prerequisites
- No "pre-start" – hardware is configured automatically and in the background
- Flexible and quick match schedule generation
- Streamlined realtime score entry
- Reports, results, and logs can be viewed from any computer
- An arbitrary number of auxiliary displays can be set up using any computer with just a web browser, to show rankings, queueing, field status, etc.
Teams may use Cheesy Arena freely for practice, scrimmages, and off-season events. See LICENSE for more details.
From a pre-built release
Download the latest release. Pre-built packages are available for Linux, macOS (x64 and M1), and Windows.
On recent versions of macOS, you may be prevented from running an app from an unidentified developer; see these instructions on how to bypass the warning.
From source
- Download Go (version 1.22 or later required)
- Clone this GitHub repository to a location of your choice
- Navigate to the repository's directory in the terminal
- Compile the code with
go build - Run the
cheesy-arenaorcheesy-arena.exebinary - Navigate to http://localhost:8080 in your browser (Google Chrome recommended)
IP address configuration
When running Cheesy Arena on a playing field with robots, set the IP address of the computer running Cheesy Arena to 10.0.100.5. By a convention baked into the FRC Driver Station software, driver stations will broadcast their presence on the network to this hardcoded address so that the FMS does not need to discover them by some other method.
When running Cheesy Arena without robots for testing or development, any IP address can be used.
Cheesy Arena is written using Go, a language developed by Google and first released in 2009. Go excels in the areas of concurrency, networking, performance, and portability, which makes it ideal for a field management system.
Cheesy Arena is implemented as a web server, with all human interaction done via browser. The graphical interfaces are implemented in HTML, JavaScript, and CSS. There are many advantages to this approach – development of new graphical elements is rapid, and no software needs to be installed other than on the server. Client web pages send commands and receive updates using WebSockets.
Bolt is used as the datastore, and making backups or transferring data from one installation to another is as simple as copying the database file.
Schedule generation is fast because pre-generated schedules are included with the code. Each schedule contains a certain number of matches per team for placeholder teams 1 through N, so generating the actual match schedule becomes a simple exercise in permuting the mapping of real teams to placeholder teams. The pre-generated schedules are checked into this repository and can be vetted in advance of any events for deviations from the randomness (and other) requirements.
Cheesy Arena includes support for, but doesn't require, networking hardware similar to that used in official FRC events. Teams are issued their own SSIDs and WPA keys, and when connected to Cheesy Arena are isolated to a VLAN which prevents any communication other than between the driver station, robot, and event server. The network hardware is reconfigured via SSH and Telnet commands for the new set of teams when each mach is loaded.
Cheesy Arena has the ability to integrate with an Allen-Bradley PLC setup similar to the one that FIRST uses, to read field sensors and control lights and motors. The PLC hardware travels with the FIRST California fields; contact your FTA for more information.
The PLC code can be found here.
Cheesy Arena has the ability to integrate with the Cypress Team Signs used at official FRC events. See the Configuring Cheesy Arena wiki page for details configurating the team signs in Cheesy Arena.
Due to the prohibitive cost of the LEDs and LED controllers used on official fields, for years in which LEDs are mandatory for a proper game experience (such as 2018), Cheesy Arena integrates with Advatek controllers and LEDs.
See the Advanced Networking wiki page for instructions on what equipment to obtain and how to configure it in order to support advanced network security.
Cheesy Arena is far from finished! You can help by:
- Writing a missing feature, and sending a pull request
- Filing any bugs or feature requests using the issue tracker
- Contributing documentation to the wiki
- Sending baked goods to Pat
Several folks have contributed pull requests. Thanks!
In addition, the following individuals have contributed to make Cheesy Arena a reality:
- Tom Bottiglieri
- James Cerar
- Kiet Chau
- Travis Covington
- Nick Eyre
- Patrick Fairbank
- Eugene Fang
- Thad House
- Ed Jordan
- Karthik Kanagasabapathy
- Ken Mitchell
- Andrew Nabors
- Jared Russell
- Ken Schenke
- Austin Schuh
- Colin Wilson