Challenges#
The agility challenges test teams’ ability to adapt to unexpected situations and system failures during competition runs. Successfully handling these challenges is crucial for maintaining high performance and achieving competitive scores.
The competition incorporates challenges to test the robustness of team systems. Teams should be able to recognize when a challenge is occurring and properly handle the situation. There are four possible challenges that can occur during a run:
Conveyor Malfunction - Inspection conveyor stops operating
Voltage Tester Malfunction - One or both voltage testers stop providing data
Vacuum Tool Malfunction - Vacuum gripper fails to grasp objects
High Priority Order - Urgent kit request with time constraints
Conveyor Malfunction#
When the conveyor malfunction challenge occurs, the inspection conveyor will pause its motion. In addition, the cell feed will pause, so no new cells can be added during the challenge.
Parameter |
Type |
Description |
---|---|---|
|
int |
Time in seconds when the malfunction begins (minimum: 0) |
|
int |
Duration in seconds the malfunction lasts (minimum: 1) |
Teams are expected to handle this challenge by:
Detecting the malfunction by monitoring the conveyor status topic (reference)
Pausing the inspection system to avoid conflicts
Waiting for recovery by monitoring the status topic until it reports operational status
Resuming operations once the conveyor and cell feed return to normal
Voltage Tester Malfunction#
When the voltage tester malfunction occurs, one or both voltage testers will stop publishing data.
Parameter |
Type |
Description |
---|---|---|
|
int |
Time in seconds when the malfunction begins |
|
int |
Duration in seconds the malfunction lasts |
|
int |
Which voltage tester is affected (1 or 2) |
Teams are expected to handle this challenge by:
Detecting the malfunction by monitoring voltage tester topics for data availability (reference)
Adapting operations to avoid using the affected voltage tester(s)
Monitoring for recovery by watching the status topic until operational status is restored
Continuing progress using any operational voltage testers to maintain productivity
Resuming full operations once all voltage testers return to operational status
Vacuum Tool Malfunction#
When the vacuum tool malfunction occurs, a specified vacuum gripper will fail during grasp attempts.
Parameter |
Type |
Description |
---|---|---|
|
int |
Which vacuum tool is affected (1 or 2) |
|
int |
Which grasp attempt will fail (minimum: 1) |
Note
TOOL: Refers to the vacuum gripper tools VG_2 and VG_4 available to assembly robot 2.
Note
GRASP_OCCURRENCE: Specifies which attempt at grasping will fail. For example, if set to 3, the first two grasp attempts will succeed normally, but the third attempt will fail and require retry.
Teams are expected to handle this challenge by:
Detecting the failure by monitoring the response from the grasp service (reference)
Repositioning the gripper by moving it away from the target object
Retrying the grasp with proper positioning and approach
High Priority Order#
When a high priority order is requested, an internal timer starts tracking completion time. Teams should minimize the time taken to submit this urgent kit request.
Parameter |
Type |
Description |
---|---|---|
|
int |
Time in seconds when the high priority order is announced |
|
string |
Unique identifier for the high priority order |
Teams are expected to handle this challenge by:
Detecting the request by monitoring the high priority order topic (reference)
Switching cell feed to begin feeding NiMH cells
Building the kit using four NiMH cells with proper voltage specifications
Delivering the kit by moving the AGV to the shipping location
Submitting the order using the high priority submission service with the correct order ID (reference)
Restoring normal operations by switching cell feed back to Li-ion batteries
Resuming standard tasks to continue regular production
Configuration Example#
For complete challenge configuration examples showing all challenge types with valid parameters, see the Challenges Configuration Reference.