Race Resources

1. Overview

The 2026 RoboRacer PNU-HYUNSONG CHAMPIONSHIP autonomous racing competition is open to teams of all levels. Participating teams may consist of up to 6 members per team, and each participant must be a member of only one team.

This competition will be held as an in-person competition from January 25 (Sun) to January 27 (Tue), 2026, at BEXCO Convention Hall, Busan.

Competition Schedule: January 25 (Sun) ~ 27 (Tue), 2026
Scale: 30 Teams (Domestic & International)
Teams can register for the competition through the official website.

Organized & Hosted by: RoboRacer Korea, Pusan National University RISE Business Group Future Mobility UIC, Pusan National University National University Development Project Future Mobility Specialization Project
Sponsored by: Hyunsong Education & Culture Foundation, Busan Shared University Future Mobility Major

2. General Competition Rules

The competition consists of the following 4 stages (stages 1-4):

• Stage 1: Registration and inspection
• Stage 2: Mapping and practice sessions (mapping, official practice, free practice)
• Stage 3: Qualification (time trial)
• Stage 4: Head-to-head race

Teams registered for in-person competition must provide and build their vehicles directly according to the constraints listed below. Additionally, each team must have a unique vehicle (i.e., one research lab cannot participate with multiple teams using one vehicle).

2.1 Vehicle Class

Vehicle class allows only vehicles that meet the following constraints:

• Vehicles must be built according to ROBORACER guidelines, but alternative parts may be allowed if they comply with regulations. Any unclear or ambiguous matters must be confirmed with the race organizers in advance.
• Each vehicle is inspected as part of the qualification to ensure it meets the standards. Vehicles that do not meet the standards cannot participate.
• This competition is an algorithm competition. Configurations that gain unfair advantages through hardware are not allowed.

• Chassis: The race is designed for 1:10 Traxxas chassis (e.g., TRA74054, TRA6804R). These chassis are recommended, but chassis within 15% of Traxxas vehicle dimensions are generally allowed (width 238mm ~ 341mm, length 454mm ~ 654mm). Both 4WD and 2WD are allowed.
• Structural modifications to the vehicle's chassis (chassis/frame) and body (including body cover/body shell) are prohibited. "Modifications" include cutting, drilling (additional drilling), grinding, bending, molding, removal/replacement of structural components, and changes to wheelbase/track width. However, non-structural attachments for safety and sensor mounting (e.g., foam bumpers, detection boxes, sensor brackets) are allowed, but must be mounted in a way that does not remove material or change the shape of the chassis/body (using existing fastening points, clamps/brackets, double-sided tape, etc.).
• Tires: No restrictions (both sponge and rubber are allowed). However, use of chemical additives is strictly prohibited.
• Main Computing Unit: Limited to NVIDIA Jetson AGX Orin or below. However, only one computing unit can be used. External GPU (eGPU), desktop/server-grade GPU, and external AI accelerators (separate PCIe/Thunderbolt-based acceleration devices, etc.) are prohibited. The interpretation of "or below" follows the organizers' interpretation, and unclear or ambiguous equipment requires prior approval.
• LiDAR: No specification restrictions. Only one LiDAR sensor can be used. 3D LiDAR is also allowed. (Note that expensive 3D LiDAR may be damaged in high-speed racing)
• Camera: Both single cameras (Logitech C270, C920, Raspberry Pi Camera V2, Arducam, etc.) and stereo cameras (Intel Realsense, ZED, etc.) are allowed. However, cameras that provide additional information such as detection results or VIO results through internal processing are not allowed. (Providing only depth information is allowed)
• Motor: Only a single motor can be used in the powertrain. Internal modifications to the motor (winding changes, rotor/magnet replacement, etc.) and processing for performance modification purposes are prohibited.
• Battery: 4S LiPo battery or 3S or below. The total number of battery cells installed on the vehicle must be 4S or less. (e.g., 2S + 2S, 4S)
• Detection Box: Vehicles must be easily detectable by the opponent's LiDAR. Therefore, the vehicle must occupy a space of at least 12×12cm in all horizontal planes between 10~30cm from the ground.
• Foam Bumper: To minimize damage in collisions, bumpers must be made of soft material. When there are two or more vehicles on the track, detection box and foam bumper must be attached.
• Other Sensors: IMU, encoders, custom ESC, etc. are allowed. However, indoor GPS sensors (e.g., Marvelmind) are not allowed.

2.2 Track and Racing Environment

• The competition is held at BEXCO, Busan.
• Track size: approximately 25m × 12m
• Floor material: Carpet

2.3 Inspection

The purpose of inspection is to verify that the autonomous vehicle's hardware meets competition requirements and is not dangerous to the environment, opponents, or people.

• Vehicles must be built according to ROBORACER guidelines. Alternative parts are allowed if they comply with regulations.
• Teams must demonstrate emergency brake operation through remote human control. (However, it cannot be used for intervention during racing)
• Vehicle inspection is conducted on the first day of the competition by race judges.
• Inspection must be completed before the time trial, and re-inspection is required if there are significant changes to hardware or algorithms.

2.4 Mapping and Practice

2.4.1 Mapping

• Each team is given approximately 5 minutes of mapping time.
• During this time, the team has exclusive use of the entire track.
• Mapping, data acquisition, and practice can all be performed during this time.
• If you do not arrive at the designated time slot, the opportunity is lost and no additional time is provided.
• Each team can prepare multiple vehicles and use them on the track.
• Teams without map files can receive maps from nearby teams, but this is not supported by the organizers.

2.4.2 Practice

• Practice consists of official practice and free practice.
• Each team can prepare multiple vehicles, but only one vehicle per team can exist on the track.
• Sample obstacles are provided.
• The organizers are not responsible for accidents that occur during practice.
• Teams involved in accidents have an obligation to explain their algorithm when requested by judges.

2.5 Pit Stop

2.5.1 General

• The pit stop zone is a designated area for adjusting parameters without removing the vehicle from the track.
• It can be used in both qualification and head-to-head races.
• When the vehicle is in the pit stop zone, computers (mouse and keyboard) can be used for re-localization and parameter updates.
• As with the general track, people standing in this area is prohibited.
• After safely entering this zone, removing the vehicle to the island for repair is not a warning situation.
• Using this zone as a driving path in autonomous racing mode is prohibited.

2.5.2 Entry

• Manual driving (human driving) can only be used to enter the pit stop zone from the manual driving area.
• Manual driving to enter the pit during head-to-head races must not cause damage to the opponent's vehicle.

2.5.3 Exit

• When exiting from the pit stop zone to the general driving area, manual driving must not be used in any way.
• Vehicles exiting from the pit stop zone to the general driving area have an obligation to protect vehicles in the general driving area.

2.6 Qualification (Time Trial)

2.6.1 General

• Both practice and qualification use the same track.
• Qualification runs for 4 minutes within a given 6 minutes.
• Qualification can start at any time within 6 minutes, but 4 minutes is not always guaranteed.
• The format may change depending on the total number of participating teams.

2.6.2 Objective

• Fastest lap time
• Maximum number of laps completed without collision

Rankings are determined for each of the two records, and the final qualification result is determined by combining the two rankings.

2.6.3 Static Obstacles

• One static obstacle is randomly placed in each obstacle area.
• Each obstacle is smaller than 0.5m × 0.5m.
• Obstacle positions are announced on the morning of qualification day and apply equally to all teams.
• Obstacles are removed in the middle of qualification time. (e.g., removed after 2 minutes in a 4-minute qualification)
• Obstacle removal is performed safely when it will not affect vehicles.

2.6.4 Invalid Records

• When a person intervenes and affects the vehicle: The lap time is invalid and the completed lap count is reset.
• When in contact with a static obstacle: The lap time is invalid and the completed lap count is reset.
• When in contact with the track but driving can continue without human intervention: Considered minor contact and the record is valid.

2.6.5 Notes

• Moving the vehicle to any arbitrary location (e.g., start line) during qualification is strictly prohibited.
• If a vehicle goes off the track and is put back in, the direction can be slightly adjusted but must be placed back at the location where it went out.
• If there was contact with the track, even if the record is not invalid, the track must be immediately restored to its original position.
• If there was contact with an obstacle, it must be immediately restored to its original position.
• All computation must be performed inside the vehicle, and data must not be transmitted to the vehicle during normal driving.
• Use of manual (human) emergency brake during normal driving is strictly prohibited.
• There are 2 islands in the track, and each island can have up to 2 people. Example configuration: (Judge1, Team member1 in Team1), (Judge2, Team member2 in Team1)

2.7 Head-to-Head Race

2.7.1 General

• Two vehicles start from different start lines positioned in opposite directions.
• A total of two static obstacles are used, and one is randomly placed in each area after all teams have completed race preparation.
• Static obstacles on the track are removed at some point after the race starts.
• Each vehicle must complete 20 laps first within the time limit while avoiding obstacles and opponents.
• Regardless of both teams' preparation status, the race starts within 10 minutes at the latest after the start preparation begins.

2.7.2 Objective

• Completing 20 laps first

2.7.3 Random Static Obstacles

• One static obstacle is randomly placed in each obstacle area.
• Each obstacle is smaller than 0.5m × 0.5m.
• Obstacle positions are determined after both vehicles have completed preparation at the start line.
• After obstacles are placed, only the start signal can be transmitted to vehicles.
• Obstacles are removed in the middle of the race.
• Static obstacles on the track are removed when the leading vehicle completes half of the required number of laps.
• The area marked with red squares indicates where static obstacles can be placed.
• Obstacle removal is performed safely when both vehicles are not affected.

2.7.4 Collisions

Collisions with Track Boundaries and Static Obstacles

• Restore the track and obstacles to their original state.
• If the race can continue, the race must continue without interruption.

Vehicle-to-Vehicle Collisions

• Do not stop the race at team discretion without the judge's stop signal.
• In collision situations where the causing vehicle is clear but no overtaking occurred, the race continues as is.
• If the victim vehicle is clear and the victim vehicle is unable to drive, the collision is severe, or the victim was overtaken, the race is stopped.

2.7.5 Notes

• Do not stop the race at team discretion without the judge's stop signal.
• All computation must be performed inside the vehicle, and data must not be transmitted to the vehicle during normal driving.
• Use of manual (human) emergency brake during normal driving is strictly prohibited.
• Vehicles violating the detection box regulations cannot participate in the race.
• There are 2 islands in the track, and each island can have up to 2 people. (Judge1, Team member in Team1), (Judge2, Team member in Team2)
• In contact/accidents occurring during side-by-side driving where there is no clear causing party, the race is not stopped.

2.8 Common Notes (Important!!)

• If driving is difficult or dangerous due to collision, immediately emergency stop the vehicle.
• All computation must be performed inside the vehicle, and data must not be transmitted to the vehicle during normal driving.
• Manual (human) emergency brake during normal driving is strictly prohibited.
• Each team can prepare multiple vehicles, but cases where more than 2 vehicles from the same team can be on the track are only during mapping time.
• Sharing one vehicle among multiple teams is strictly prohibited.
• When 2 or more vehicles can exist on the track, detection box is mandatory. (e.g., not required during mapping/qualification)
• Complaints regarding Wi-Fi are not accepted. Autonomous systems must be designed to operate independently regardless of Wi-Fi environment. You can request teams not participating in the race to turn off their Wi-Fi, but this is for visualization/debugging convenience and does not guarantee algorithm performance.
• All hardware repairs and maintenance on the track (component repair, sensor recalibration, battery replacement, etc.) are prohibited. (Including pit stop area)
• Time slots for mapping, official practice, and qualification may vary depending on the number of participating teams.
• Time slots for mapping and official practice sessions are allocated on a first-come, first-served basis, and only teams that have completed registration and inspection can apply.
• People standing on the track is prohibited. (Except during mapping time)
• Use of joystick or pressing joystick buttons during racing is not allowed.
• The autonomous driving <-> human control switching module must be an on/off toggle method, not a "press and hold" method.
• Only one laptop can be connected for visualization (RViz, etc.) or debugging purposes.
• If too close to an obstacle ahead (opponent vehicle or static obstacle) making avoidance maneuvers impossible, you can request the judge to move back slightly.

2.9 Technical Summary Submission

2.9.1 Purpose

This regulation establishes the obligation for pre-submission of materials and presentation by excellent teams to systematically record and share participating teams' technical approaches, and to officially introduce excellent technical and operational cases before the awards ceremony, thereby enhancing the educational and research value of the competition.

2.9.2 Technical Summary Slide Submission (Mandatory for All Teams)

2.9.2.1 Submission Target

All participating teams must submit technical summary slides by the deadline specified by the competition.

2.9.2.2 Submission Format and Length

• Format: Slides (PDF or PPTX)
• Length: Within 10 pages
• Language: Korean or English (as per competition announcement)

2.9.2.3 Required Content

Slides must include at least the following items:

• Team/Vehicle Overview: Team name, vehicle version, sensor configuration
• Driving Algorithm Core Summary: Core ideas and driving strategy (1 page recommended)
• System Configuration: Overall architecture and main components (including core packages/nodes)
• Interface and Operation Logic: Main inputs/outputs (topics/periods, etc.) and Pit/Mission response (if applicable)
• Safety and Verification: Fail-safe/exception handling + verification methods and result summary

2.9.3 Technical Presentation by Excellent Evaluation Teams (Before Awards Ceremony, Mandatory Presentation)

2.9.3.1 Presentation Timing (Important)

• Technical presentations are not operated as qualification technical sessions.
• Technical presentations are conducted in official sessions from after provisional ranking calculation (or including result verification stage after competition ends) until before the awards ceremony begins.
• The exact schedule (session start/end time) will be announced by the organizers on the day.

2.9.3.2 Presentation Target (Excellent Evaluation Teams)

• The presentation target is "excellent evaluation teams" selected according to criteria determined by the organizers, regardless of final ranking.
• Number of excellent evaluation teams: Organizer announcement (recommended: 3~8 teams)

2.9.3.3 Excellent Evaluation Criteria (Examples, Finalized by Organizers)

The organizers may select excellent evaluation teams based on some or all of the following items:

• Performance: Lap time, stability, penalty minimization, completion rate
• Technical Quality: Clarity of Pit Zone response logic, structural design (modularization), real-time considerations
• Safety: Risk situation response, collision/departure minimization, fail-safe implementation
• Reproducibility/Explainability: Clarity of submitted slides, consistency of structure, ability to explain core packages/pipelines
• Innovation: New approaches (e.g., speed policy, state machine, local planning, sensor fusion, etc.)

※ "Excellent evaluation criteria and selection method" will be finalized through competition announcement.

2.9.3.4 Presentation Obligation and Format

• Excellent evaluation teams have a mandatory presentation obligation and must provide presentation materials and perform the presentation when requested.
• Presentation Materials: Based on the submitted slides within 10 pages, but partial modifications for pre-awards ceremony presentation are allowed (maintaining within 10 pages recommended)
• Presentation Time: Within 10 minutes per team (whether Q&A is included will be announced by organizers)

2.9.3.5 Measures for Non-compliance

If presentation is refused or performed insincerely without justifiable reason, the organizers may apply some of the following measures (finalized through competition announcement):

• Cancelation of excellent evaluation selection (exclusion from presentation target)
• Exclusion from special awards/category awards candidates
• Exclusion from official competition records/promotional materials
• Non-payment of prize money
• Other sanctions determined by organizers

3. Warnings and Penalties

Judgments on incidents are at the discretion of on-site judges, and all teams must respect this. Even if an incident includes multiple violations, only one penalty per incident is applied.

3.1 Qualification

3.1.1 One Rank Demotion

In the following cases, a one rank demotion penalty is applied to the qualification result.

• Using keyboard or mouse during racing (prohibited even if no data transmission occurs)
  • Exception 1: When the vehicle is not on the track
  • Exception 2: When in the pit stop area
  • Exception 3: When transmitting initial guess for re-localization
• Manual intervention (joystick, keyboard, other devices) on own vehicle
  • Exception 1: When judge declares race stop and emergency stop is necessary
  • Exception 2: When delivering start signal for start/restart
  • Exception 3: When emergency stop is necessary due to driving impossibility from collision
  • Exception 4: Driving in manual driving area for entering pit stop area
  • Exception 5: When emergency stop is necessary after being stuck in obstacle for more than 5 seconds
  • Exception 6: Emergency stop to prevent abnormal driving such as sudden acceleration or reverse driving
  • Exception 7: When judge allows manual intervention because opponent vehicle severely damaged the track making driving impossible
  • Exception 8: When stopping after qualification ends
• When a person directly creates or selects a modified path based on obstacle positions during racing

3.2 Head-to-Head Race

3.2.1 Additional 1 Lap

In the following cases, an additional 1 lap penalty is given.

• Accumulation of 3 warnings
• Fatal interference by a person with the opponent vehicle during racing
• When going to fix the track causes physical contact with the opponent vehicle affecting driving
• Accident with large impact in complete rear-end collision
• Accident with large impact even if not a complete rear-end collision
• Using keyboard or mouse during racing (prohibited even if no data transmission occurs)
  • Exception 1: When the vehicle is not on the track
  • Exception 2: When in the pit stop area
  • Exception 3: When putting the vehicle back on the track after going off and transmitting initial guess for re-localization
• Manual intervention on own vehicle
  • Exception 1: When judge declares race stop and emergency stop is necessary
  • Exception 2: After start, restart, or end
  • Exception 3: When driving is impossible due to collision
  • Exception 4: When in manual driving area for pit entry for pit stop
  • Exception 5: When stopping to change to manual operation after being stuck in obstacle for more than 5 seconds
  • Exception 6: Emergency stop to prevent abnormal driving such as sudden acceleration or reverse driving
• When a person directly creates or selects a modified path based on obstacle positions during racing

3.2.2 Warning 1 Time

In the following cases, warning 1 time is given.

• False start
• Not actively restoring the track
• When completely passing through the pit stop zone in autonomous racing mode
• When detection box fixation is not properly done during racing (Exception: If fixed in pit stop zone and driving resumed within 1 lap after warning. New warning may be given if not fixed every lap)
• Intervention on own vehicle during racing
  • Removing vehicle outside the track after collision
  • Directly modifying vehicle heading
• Interference by a person with opponent vehicle during racing
  • When going to fix the track is detected by opponent vehicle's detection module affecting driving
  • When there is a clear causing vehicle and victim vehicle, and the victim vehicle becomes unable to drive (e.g., small collision but victim vehicle spins and is overtaken)

3.2.3 Example Cases

Detailed example cases may be provided through on-site judge briefing or separate documents.

2.5 Power System

• Battery specifications are provided in the build manual
• Maximum voltage: 14.8V (4S LiPo)
• Batteries must be safely secured with appropriate protection devices
• Battery Management System (BMS) use is recommended
• Teams must bring sufficient batteries for the competition

2.6 Drive System

• Standard servo motor for steering (specifications provided)
• Brushless DC motor for propulsion (specifications provided)
• Electronic Speed Controller (ESC) must comply with specifications

3. Software Requirements

Software and Computing

• Open-source RoboRacer ROS2 stack is provided
• Teams can modify and extend the provided software stack
• All software must be autonomous and remote control is prohibited
• Emergency stop functionality must be implemented
• Code submission may be required upon request from organizers

4. Competition Format

Competition Track

4.1 Qualification Session

• All teams participate in time trial qualification
• Each team can attempt multiple times (number of attempts to be announced)
• Objective: Complete a lap without collision with track boundaries
• Qualification times are used to determine seeding for tournament stage
• Teams must complete at least 1 valid lap to pass qualification

4.2 Tournament Stage

• Teams that pass qualification participate in 1-on-1 racing
• Bracket format based on qualification seeding
• Each match consists of multiple laps
• Winner advances to next round
• Loser is eliminated.

5. Track Rules

Race Track

• Track layout is announced on the day of competition
• Track boundaries are clearly marked
• Vehicles must always remain within track boundaries
• Contact with track boundaries results in invalid lap
• Track may include obstacles and dynamic elements
• Track conditions may change during competition

6. Safety Rules

• All vehicles must pass technical inspection before competition
• Emergency stop functionality must be operational and accessible
• Teams must comply with all safety protocols during competition
• Safety equipment (gloves, safety goggles) must be worn in pit area
• Unsafe behavior results in immediate disqualification
• Organizers have the right to immediately stop vehicles deemed unsafe

7. Technical Inspection

• All vehicles must pass technical inspection on January 25, 2026
• Inspection items: dimensions, weight, safety features, sensor functionality
• Vehicle inspection must be completed within the designated time.
• Vehicles that fail technical inspection cannot participate in competition events.

8. Scoring System

8.1 Qualification Scoring

Scoring Area 1: Achieve fastest lap time without collision

• Invalid laps (boundary violations) are not counted

Scoring Area 2: Achieve maximum cumulative number of laps without collision

8.2 Tournament Scoring

• Winner of each match advances to next round
• Winner is determined by: team that completes first,

9. Disqualification

• Technical specification violations
• Safety rule violations
• Unsportsmanlike conduct
• Interference with other team vehicles
• Use of prohibited equipment or software
• Failure to comply with organizer instructions
• Disqualification decisions are final and cannot be appealed

10. Code of Conduct

• All participants must maintain professional and respectful behavior
• Teams must respect other teams and organizers
• All acts of cheating or unfair advantage are prohibited
• Teams must follow all instructions from competition officials
• Code of conduct violations may result in disqualification

11. Appeals and Disputes

• All competition decisions are made by the organizing committee
• Appeals must be submitted in writing within 30 minutes of the decision
• Appeals are reviewed by the technical committee
• Final decisions are binding

12. Additional Information

• Detailed competition manual is provided after registration
• Track specifications are provided before competition
• Rule changes are notified to all registered teams
• Organizers reserve the right to modify rules as necessary
• Please contact the organizing committee for inquiries