Thank you to all the teams that applied to be part of the first round of Alpha Testing for the new SystemCore robot controller. With over 400 wonderful applications eligible for this round, narrowing it down to 50 selections was not easy.
Device Updates
In advance of teams getting their hands on Alpha units, there are a few more details we wanted to share that weren’t part of the previous blog. Just like the details shared in that blog, these details represent the current status of the design and are subject to change as a result of Alpha testing. First, here’s an image of the device:
In addition to the ports described in the previous blog, you’ll notice another major feature in the image, a small screen. This screen displays helpful diagnostic information to make SystemCore easy to use and troubleshoot. We plan to develop and refine the information displayed on the screen based on feedback from teams and event volunteers as we move through the testing process.SystemCore is 5.3 in x 2.8 in. x 1.1 in. (135.3mm x 71.5mm x 28.13mm) and weighs approximately 0.475 lb (215 g). Here’s a dimensioned drawing of the device:
There has also been substantial progress on the software. This video shows some of the development on the web interface, including the controller-hosted programming environments and device status information:
webAlpha Testing
Selection of Alpha testing teams for the first wave was focused on FIRST ® Robotics Competition teams and was based on a variety of factors including, but not limited to:
- Geography (ensure geographic spread, especially among different spoken languages)
- Current programming language (ensure some teams using C++ and Python)
- FIRST ® Tech Challenge program participation (although only SystemCore is currently available, we don’t want to wait a few months before we start getting any FIRST Tech Challenge student feedback)
- Team’s answer to “why should we be selected”
The following 50 applications have been selected to participate in the first wave of Alpha testing, beginning soon. Teams that have been selected have received an email to the address included in their application with additional details on testing and next steps. Applications are listed numerically by the lowest FIRST Robotics Competition team number included, applications that also indicated FIRST Tech Challenge participation are marked with an *.
Team Number Team/Org Name Country State/Province 27* Team RUSH US Michigan 67 The HOT Team US Michigan 100 The WildHats US California 180* S.P.A.M. US Florida 190 Gompei and the HERD US Massachusetts 195* CyberKnights US Connecticut 302* The Dragons US Michigan 321, 427* Robolancers/LANCE-A-LOT US Pennsylvania 456* Siege Robotics US Mississippi 461* Westside Boiler Invasion US Indiana 604 Quixilver US California 694* StuyPulse US New York 836 The RoboBees US Maryland 1156* Under Control Brazil Rio Grande do Sul 1619* Up-A-Creek Robotics US Colorado 1678 Citrus Circuits US California 1716, 3381, 4531, 5586, 7103, 7619, 9578* Lakeshore FIRST Robotics & Brown County FIRST Robotics US Wisconsin 1736 Robot Casserole US Illinois 1778* Chill Out US Washington 1987* Broncobots US Missouri 2052 KnightKrawler US Minnesota 2403, 4146, 9432 Sabercat Robotics US Arizona 2718* Team OKC e’possums (Σ 1/n! x 10^3) US Oklahoma 2724, 3506* YETI Robotics US North Carolina 2974 Walton Robotics US Georgia 3015 Ranger Robotics US New York 3075* Ha-Dream Team Israel Merkaz 3504* Girls of Steel US Pennsylvania 3538* RoboJackets US Michigan 3847 Spectrum -△◅ US Texas 3990 Tech for Kids Canada Quebec 4061 SciBorgs US New York 4069* Lo-Ellen Robotics Canada Ontario 4270 Crusaders US Hawaii 4481* Team Rembrandts Netherlands Noord-Brabant 4607* C.I.S. US Minnesota 4774 The Drop Bears Australia New South Wales 4917 Sir Lancerbot Canada Ontario 5113 Combustible Lemons US New Jersey 5515* Blue Power Robotics China Shanghai 5940 BREAD US California 6328 Mechanical Advantage US Massachusetts 6391 Ursaline Bearbotics US Missouri 6459* AG Robotik Türkiye İstanbul 7130 Future Shock Chinese Taipei Taichung 8795* Chaotics Türkiye Ankara 9128, 9752, 10340* ITKAN Robotics US Texas 9134* Tecmilenio - DEVOLT Mexico Chihuahua 9194* Gemin√-1s US Ohio 9593* Rhinos Mexico Mexico City Teams that were not selected will automatically be considered for selection in the second wave of testing, expected to begin in September. Any additional teams wishing to apply for this wave can use the application form. While this wave will be mostly focused on adding FIRST Tech Challenge teams due to the MotionCore hardware becoming available, a limited number of FIRST Robotics Competition spots may be available based on some first wave Alpha teams transitioning to FIRST Tech Challenge testing.
Teams can follow along with Alpha testing in this Github project. We can’t wait to hear team’s feedback once they get their hands on the device and will share more updates about MotionCore and Wave 2 of Alpha Testing in approximately August/September!
This video was also posted recently on the same channel as the video linked. terminal+iperf
Was this shared anywhere?
We’re incredibly thankful to have been accepted as one of the alpha test teams - we are looking forward to sharing as much as we can about our experience with the SystemCore!
In addition to the ports described in the previous blog, you’ll notice another major feature in the image, a small screen. This screen displays helpful diagnostic information to make SystemCore easy to use and troubleshoot.
How long until someone gets Doom running on it?
Does anyone know if these would work at 2025 offseasons? 
Hoping someone is able to run them on field.
Does the screen have more color options than a pregnancy test?
They do seem like strange placement. I wish they color code the CAN release buttons. Its not feasible but would be a nice touch
The email says they would like us to run SystemCore “in competition (where possible)” so I’m assuming yes. We will be planning to run ours at our remaining offseason competitions if so.
RIP Labview, you will not be missed.
Hopefully it’s not the Tim Allen version:
I do want to ask the community, what are y’all’s thoughts on only 6 SmartIO ports? I have mixed feelings about it
So few teams use IO anymore, that I think its fine. Supporting more protected IO gets expensive fast, especially when the numbers really do show its not necessary anymore.
6 more than it needs
bad take.
Perhaps for teams with many resources, and those more likely to be found on Chief Delphi, all interaction with devices is done over the CAN bus. However, the ability to read PWM sensors, drive PWM motor controllers, wire beam breaks and limit switches directly to the controller is important, especially for teams who can’t necessarily afford to buy all the new CAN devices.
Considering the awkward positioning, I’d guess they’re more for expansion boards than for standard cable retention, which feels like an oversight to me. At least I suppose it shouldn’t be too hard to 3d print adapters to hold your cables?
Everything in the KOP now supports CAN, and there only exists a single motor controller currently on the market that supports PWM only. Even the kitbot instructions wire with CAN. So driving motor controllers is really not something PWM needs to do anymore IMO. It’s supported, but I wouldn’t expect it to be common, even among lower resource teams.
Who says a bus based expansion for digital IO needs to be expensive and prohibitive for teams?
I think you mean, hopefully, it runs the best version of Doom!