ASU F1TENTH Progress
ASU F1TENTH
What is F1TENTH?
Rules
Status at the beginning of the season
- Team technically started at the last season
- Previous season had only 8 members and that season was mostly research and simulation
- Only Belal and I continued from previous season
- Car was just a chassis with motor
Upgrades this season
Goal
- Setting the foundation at our university for continuous contribution F1TENTH research community by being the first F1TENTH group at ASU that gets the team participate in ICRA 2026 Roboracer competition (we are also targeting the offline competition)
- Becoming a pioneering F1TENTH team that not only competes internationally but shapes the future of autonomous racing through original research, open-source contributions, and a culture of relentless learning and technical excellence.
Community
- Managed to excite people and creating a community of 28 members
- Creating a live knowledge wiki to help more F1TENTH teams participate in the competition as we share what we know
Hardware
- Power PCB designed and fabricated
- Sourced a Raspberry Pi
- Sourced RP LiDAR A1
- Fabricated the platform deck to hold our autonomous hardware
Software
Master-level course finishing
- RoboRacer
Top-tier stack analysis and learning - ForzaETH/race_stack: The autonomous racing stack for the ForzaETH team at PBL
Low-level and High-level
- Implemented the micro-ROS low level app for commanding the car
- Implemented the high level interface with the low level
High-level
Simulation
- Getting started with the basic simulation and developing two main algorithms
- FTG
- RRT
- Getting the official, advanced competition simulator (AutoDrive) to run successfully
Limitations and Challenges
- Hardware was not available to create an autonomous stack that implements the complete autonomous modules, so we defaulted to an efficient autonomous algorithm, called FTG, that uses the hardware we have to get the car driving autonomously
- Exams rescheduling lead to constricting the timeline so we had to target the Korea conference
- Having to write our own hardware interface instead of micro-ROS to solve bugs that were not clear