The fifth year was a pivotal one for Buckeye AutoDrive. On one hand, it marked the final year of the competition series. On the other, the team was contending with the disastrous failure of its vehicle in the previous year's competition.Â
Over the summer, our advisors set a goal for the team to complete a simplified MVP demo based on the fourth-year competition, aiming to validate our teamwork and test our ability to execute the required tasks. Ultimately, these tasks were completed.
Team members returning from recent competitions are determined to draw upon their experiences and press ahead with renewed vigor as they head into their final year in the competition.
September was a month for laying the groundwork. Core members focused on interpreting the rulebook and formulating the annual plan, while team members who had worked diligently throughout the summer continued to pursue their original objectives. Simultaneously, the team conducted a new round of recruitment.
9/22: Initial HMI Concept
9/22: Legacy Pipeline Testing Plan
9/22: Legacy Pipeline Testing Plans and Results
The new rulebook suggested that teams were permitted to use computing units such as the NVIDIA Jetson instead of relying on the originally provided server, which significantly enhanced flexibility.Â
Given the concern that rival teams might upgrade their computing power and sensors, the team decided to switch to a completely different compute platforms and software stack amid the changes in rules.
10/6: Initial Safety Checks Code Demostration
10/13: Initial Pedestrian Robot Design
10/13: Initial HMI GUI Demonstration
10/20: Stop Sign Logic Test
Requirements regarding LiDAR have also been significantly relaxed. The previously mandated LiDARs, which were not reliable, are no longer required. Instead, teams are allowed to use advanced LiDARs available on the market.
However, despite the various issues with the original LiDAR, all previous development was based on it. After a difficult decision, the team proceeded with the original development in parallel with the lengthy approval and procurement process for the new LiDAR.
11/10: HMI Map Demostration
11/17: PID and Smoother Velocity Testing
11/24: Localization Testing with FAST-LIO2 data
11/24: Perception 2D + 3D Tracking
As the autumn semester draws to a close, the team members are heading home. Meanwhile, the procurement of the new LiDAR unit is still in progress.
12/1: Perception 2D + 3D Benchmark
12/1: Further Investigation on Acceleration Smoothness
January is a month of transition. During the winter break, many students graduate and hand over their responsibilities, passing the torch to core members and promising newcomers. The new hardware changes have been finalized, the computing platform has undergone preliminary testing, and the new LiDAR was shipped.
The team has had a busy month. The new LiDAR has arrived, and testing is in full swing. Meanwhile, the new HMI has also been successfully installed. The Winter Workshop also took place during this time, with some team members traveling to Michigan to give presentations and learn about rule updates. As the DYOC deadline approached, the team headed to TRC to conduct field tests.
2/2: HMI Installed
2/16: New LiDAR Mounted
2/16: New LiDAR Initial Test
2/16: New LiDAR Data CollectionÂ
2/23: New Blue Light Code Tested
2/17: Winter Workshop
2/23: DYOC Plans
Throughout March, the various components matured, and the team gradually shifted from high-intensity development to field testing and issue resolution. However, the incident on March 9 brought the team's testing to a standstill. The newly acquired LiDAR unit was accidentally damaged just one month after purchase. The team leader and the advisor held a meeting and conducted a vote. The team ultimately decided to purchase a used, previous-generation LiDAR for immediate use while simultaneously seeking after-sales support. A used LiDAR unit was quickly purchased, installed, and tested. The conclusion was that performance was largely unaffected.
3/2: HMI Map Testing
3/2: Right Turn Only Sign Testing
3/9: LiDAR Cable Damage
3/9: LiDAR Unit Damage
3/29: On-site GNSS Interference Adjustments
3/29: A Successful Run of DYOC
With the completion of DYOC, the team's work should have been winding down. However, tuning for the diverse road conditions encountered during the competition and the SLAM development remained unfinished. The team continued to push forward, fulfilling one requirement after another.
4/5: LiDAR Test
4/6: HMI Break Activation
4/20: Ethernet Port on the Driver's Side
4/20: Cable Protection Cap
As the competition approaches, the team is finalizing the work. To address potential unreliability in the SLAM system, the team has developed an additional positioning system based on CAN data. All components undergo repeated testing to ensure maturity.
5/13: Perception Frame Rate Telemetry
5/13: Perception 3D Objects
5/13: Alternative CAN Based Localization
5/13: Pedestrian Avoidance Testing
From May 31 through June 6, 2026, the team had it's Validation Event, also refer as the final competition, in Ann Arbor, Michigan. Details regarding the Validation Event can be found on the following pages.