A field management system that just works.
For 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.
For teams
- Uses cheaper hardware (no modbus!)
- Allows for less wiring (just additional ethernet cable to alliance stations + one for amps)
- You don't have to program a PLC
This was made almost in whole by FRC Team 254. Team 3256 has just modified it to work better for our resources and budgets.
Teams may use Warrior 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
Warrior-arenaorWarrior-arena.exebinary - Navigate to http://localhost:8080 in your browser (Google Chrome recommended)
IP address configuration
When running Warrior Arena on a playing field with robots, set the IP address of the computer running Warrior 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 Warrior Arena without robots for testing or development, any IP address can be used.
When using raspberry pis for alliance station buttons and scoring, the following IPs should be used
| Raspberry Pi Location | IP Address |
|---|---|
| Red Alliance Driver Station | 10.0.101.0 |
| Blue Alliance Driver Station | 10.0.101.1 |
| Reserved For Auto Scoring | 10.0.101.2 |
| Reserved For Auto Scoring | 10.0.101.3 |
| Reserved For Auto Scoring | 10.0.101.4 |
| Reserved For Auto Scoring | 10.0.101.5 |
Warrior 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.
Warrior 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.
Warrior 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 Warrior 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.
Warrior Arena has the ability to connect to Raspberry Pis (or similar SBCs) instead of using a PLC. Both all driver stations have an E-Stop and an A-Stop, with one RPi per alliance. Additionally, one RPi per major section of the game, that isn't connected to the driver stations (note: certain years, 2025 for example, don't have auto scoring, thus only use the two driver station RPis)
The RPi code can be found here.
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), Warrior 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.
Warrior Arena is far from finished! You can help by:
- Checking out the TODO list, 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 Warrior 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