> For the complete documentation index, see [llms.txt](https://robonation.gitbook.io/robotx-2026-team-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robonation.gitbook.io/robotx-2026-team-handbook/section-3-autonomy-challenge/3.2-mandatory-activities.md). # 3.2 Mandatory Activities Prior to being permitted to operate in any competition areas (on land or in water), each autonomous system must pass basic functionality and safety checks. These include verification that the systems meet vehicle requirements as specified in [Section 5.3 System Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements.md), as well as demonstration of the operation of all safety systems. Vehicles are weighed before each scoring run. Teams transport the vehicle on their cart to the scale for weight measurement. Any system operating in autonomy courses must report status and other required data via the RoboCommand system as specified in [Section 3.4 Communications Protocol](/robotx-2026-team-handbook/section-3-autonomy-challenge/3.4-communications-protocol.md). ## **3.2.1 Static Safety Inspection** Prior to deploying at the competition, all systems must meet all safety requirements and pass a safety inspection, as outlined in [5.2 Safety Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.2-safety-requirements.md). Any system that is deemed unsafe may be disqualified. At a minimum, the following requirements are checked: * Emergency Stop System (location of switches, on-board and remote functionality). * Tow points and tow line are installed and clearly marked (forward/aft). * Lift points are clearly marked and lifting harness is sufficient. * Safety requirements for propellors, including propeller guards. * All components or subsystems are properly secured. * Mount points and compatibility to carry emergency recovery light. * Cart meets published transport requirements. More details on safety and system requirements are available in [5.2 Safety Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.2-safety-requirements.md) and [5.3 System Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements.md). ### USV Functionality and Safety Checks Teams must demonstrate that each USV adheres to the system requirements outlined in [5.3.1 USV Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements/5.3.1-usv-requirements.md) and pass the static safety inspection and weight measurement. ### UUV Functionality and Safety Teams must demonstrate that each UUV adheres to the system requirements outlined in [5.3.2 UUV Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements/5.3.2-uuv-requirements.md) and pass the static safety inspection and weight measurement. ### UAV Functionality and Safety The [Civil Aviation Authority of Singapore (CAAS)](https://www.caas.gov.sg/public-passengers/unmanned-aircraft) serves as Singapore's national aviation authority, responsible for safety and air traffic management. Teams must meet all requirements mandated by the CAAS for their UAV. Compliance with CAAS regulations will be collected in the [UAV Proof of Readiness](https://robonation.gitbook.io/robotx-2026-team-handbook/section-3-autonomy-challenge/pages/HL3g28nPzPvt82HdYnz6#id-3.1.4-uav-and-pilot-proof-of-readiness-criteria), required of teams prior to competition. **UAV Airworthiness Safety Inspection** Prior to being cleared for flight, the UAV must pass the airworthiness safety inspection. At a minimum, the following requirements will be checked: * Meets the limitations for size and weight. * Safety issues related to, but not limited to, propellers, motor mounts, general airframe and wiring integrity, battery security, and battery capacity checks. * All sub-systems are properly secured. * Autonomous flight control disconnected to enable manual flight control mode. * Mount points and compatibility to carry emergency recovery light. More details on system requirements are available in [Section 5.3.3 UAV Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements/5.3.3-uav-requirements.md). {% hint style="info" %} The requirements for UAV Functionality and Safety are still being finalized and will be provided at a later date. {% endhint %} ## **3.2.2 Weight Measurement** Systems are weighed at the start of competition to ensure compliance with the [system requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements.md). Teams transport the vehicle on their cart to the scale (similar to a veterinary scale, available at [scaleline.com](http://scaleline.com/vet_scale.htm?gclid=CjwKCAiA-9uNBhBTEiwAN3IlNL38ZIrZjTkdl4690noFTr8LZWN7jzHxL1QlvW9r-muZxQ7h6n-5jRoCvdcQAvD_BwE)) for weight measurement. The stable scale reading weight is recorded. During scored runs, the systems must be re-weighed every time it is launched into the water. If the system stays in the water between scored runs, teams may forgo the weight test a second time. However, if a team is observed to be switching significant components or making modifications on their boat, the team may be asked for a new measurement. ### Weight & Size Requirements Weight and size requirements can be found in the following sections: * [5.3.1 USV Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements/5.3.1-usv-requirements.md) * [5.3.2 UUV Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements/5.3.2-uuv-requirements.md) * [5.3.3 UAV Requirements](/robotx-2026-team-handbook/section-5-rules-and-requirements/5.3-system-requirements/5.3.3-uav-requirements.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://robonation.gitbook.io/robotx-2026-team-handbook/section-3-autonomy-challenge/3.2-mandatory-activities.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.