arrow-left

All pages
gitbookPowered by GitBook
1 of 7

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Team ID List

Team ID
School/Organization
Team Name

ALDA

Adana Alparslan Türkeş Science and Technology University

KAAN Technology Club

ASTA

Advancing Science Technology and Art

Team Inspiration

AGHK

AGH University of Krakow

AGH Solar Boat Team

ALAN

Alanya Alaaddin Keykubat University

ZeroneTech Kılıç

BEAV

Beaver Country Day School

BeaverAUV

BENE

Benedict College

B Sea Bots

CBRZ

Calibrator-Z

Bluewave 2.O

CRNL

Cornell University

Cornell Autoboat

DOBG

Dreams of Bangladesh

DoB JolJan

ERAU

Embry-Riddle Aeronautical University

Team Minion

FLAU

Florida Atlantic University

Owltonomous

FSUP

Florida State University (Panama City)

NoleNavigators

GDSK

Gdańsk University of Technology

Science Club SimLE

GTEC

Georgia Institute of Technology

Marine Robotics Group

HUMB

Humber Polytechnic

Humber ASV

ITSN

Institut Teknologi Sepuluh Nopember

Barunastra ITS

JMHS

James Martin High School

MHS SEALs

KNYT1

Konya Teknik Üniversitesi

Kapsül Yazgit EternalKNY

KNYT2

Konya Technical University

Kapsul Yazgit Pruva

KYUT

Kyushu Institute of Technology

OUXT-Polaris

LSSU

Lake Superior State University

Team AMORE

MITB

Massachusetts Institute of Technology

MIT Arcturus

MUNC

Memorial University of Newfoundland

Iceberg ASV

MTCW

Military Technical College

MW

NAVR

Navier USN

Navier USN

PIRI

Piri Reis University/PRU-İDA

PRU-İDA

PNMI

Polynomial Institute

TORONGO

QUEU

Queen's University

aQuatonomous

TAUT

Tech Autocrats

BengalBoat

TDMY

Tecnológico de Monterrey

VantTec

TNAV

Turkish Naval Academy

BlueHomeland

USBM

Universitas Sebelas Maret

Bengawan UV Team

UCFH

University of Central Florida and Hagerty High School

The Water Dogs

ULLY

University of Louisiana at Lafayette

Team Katrina

UMCH

University of Michigan

UM::Autonomy

UPIT

University of Pittsburgh

Pittsburgh Electric Propulsion

UPRM

University of Puerto Rico Mayaguez

Roboboat UPRM

3.4 Qualifying Round

Three Qualifying and Practice Courses are available for teams to practice, demonstrate proficiency, and qualify for the Semi-Finals Round. These courses consist of all six (6) tasks. Multiple teams may be on a Qualifying and Practice Course at the same time. Teams may schedule times to practice or complete individual tasks on these courses with the Technical Director. Teams may attempt completion on individual tasks in any order.

Qualification Criteria | To qualify for Semi-Finals, the ASV must complete:

  • core capabilities of two (2) individual tasks

  • advanced capabilities of two (2) individual tasks

  • two (2) tasks in sequence autonomously

  • send heartbeat message

3.2 Task Descriptions

This section provides details of the tasks in the Autonomy Challenge. Teams are encouraged to develop a strategy approaching these tasks that best suits the capabilities of their ASV.

hashtag
Storm Response: Technology in Action for Recovery and Relief

The 2026 Mission is based on the following scenario: operations in a harbor environment recovering from a major storm. ASVs are used to demonstrate surface navigation, debris avoidance, target identification, and collaborative behaviors as they contribute to restoring marine operations and responding to critical zones.

  • Assessment & Discovery: Tasks involving obstacle navigation, pylon inspection, and wreckage/debris identification simulate the urgent need for rapid assessment of damage following a storm. These missions reflect how autonomous vessels might support situational awareness in dangerous or hard-to-reach environments.

  • Recovery & Delivery: Tasks like Emergency Response Sprint and Harbor Alert mimic real-world missions where rapid action is necessary to prevent further harm and begin rebuilding efforts. These simulate coordination with relief teams and accurate, repeatable delivery of materials.

  • Environmental & Public Safety: Debris Clearance and Navigate the Marina tasks simulate crucial post-disaster actions—like identifying water contamination and clearing navigation hazards—that help restore safe conditions for both rescue teams and the public.

hashtag
3.2.1 Task 1 - Evacuation Route & Return

hashtag
Entry & Exit Gates

The Evacuation Route and Return task is a navigation demonstration showcasing the basic autonomous control and sensing capabilities. The ASV must autonomously navigate through two pairs of red and green buoys. The entire ASV must pass through both sets of the gates, without touching the buoys. The ASV must start its autonomous navigation a minimum of 6 ft. before the first set of gates.

During the : This task is mandatory for all teams to qualify for semi-finals and is required to be completed first during each scored run. Additional points may be earned for exiting through gates at the end of the run.

hashtag
Capability Matrix

  • Core: Navigate through two pairs of gates

No Advanced or Disruptive levels for this task.

hashtag
Communications & Reporting

The ASV reports on the following for this task:

  • Time and position of completion of entry gates (start of run)

  • Time and position of completion of exit gates (end of run)

Defined reporting guidelines are available in .

hashtag
Task Elements

Buoys are supplied from Taylor Made, .

Task Element
Description
Model No.
Color
Height
Diameter

hashtag
3.2.2 Task 2 - Debris Clearance

hashtag
Navigation Channel

The Debris Clearance task simulates designated emergency boat lanes cleared after a storm, to enter a debris field. The ASV must sense and maneuver through the channel, staying within the defined pathway, and avoiding contact with obstacles along the way. The ASV enters the debris field and scans for floating debris hazards (black buoy represents debris; dynamic scattered color indicator buoys):

  • Red color indicator = hazard to avoid and report location

  • Green color indicator = survivor to rescue, circle (full 360), and report

After scanning and reporting hazards in debris field, the ASV returns through the channel.

The task consists of multiple sets of gates designated by pairs of red and green buoys. The debris field is made up of black obstacle buoys and .

hashtag
Capability Matrix

  • Core: Transit channel, enter debris field, avoid debris, and return through channel.

  • Advanced: Detect and interact correctly with red or green debris.

  • Disruptive: Reports location (lat/long) of all debris (color indicator buoys and black buoys).

hashtag
Communications & Reporting

The ASV reports on the following for this task:

  • Color and location of color indicators

  • Location of all buoys in the debris field

Defined reporting guidelines are available in .

hashtag
Task Elements

Buoys are supplied from Polyform US, .

Task Element
Description
Model No.
Color
Height
Diameter.

hashtag
3.2.3 Task 3 - Emergency Response Sprint

hashtag
Speed Challenge

The ASV must locate the entrance/exit gate marked by green and red buoys. ASV passes through the gate buoys, maneuvers around the yellow buoy as specified by the color indicator, and exits through the gate buoys, as quickly as possible.

  • Red color indicator = circle the buoy from the right (counter-clockwise)

  • Green color indicator = circle the buoy from the left (clockwise)

The ASV demonstrates the ability to rapidly sense the task elements with visual recognition and decision making. This task demonstrates hull form efficiency coupled with its propulsion system, and the resulting maneuverability.

hashtag
Capability Matrix:

  • Core: Pass through gate, circle yellow buoy, and exit through gate.

  • Advanced: Circle yellow buoy in correct direction indicated by color indicator buoy.

  • Disruptive: Report color of indicator and time of response.

hashtag
Communications

The ASV reports on the following for this task:

  • Color of color indicator

  • Time to complete task

Defined reporting guidelines are available in .

hashtag
Task Elements

Buoys are supplied from Polyform US, .

Task Element
Description
Model No.
Color
Height
Diameter.

hashtag
3.2.4 Task 4 - Supply Drop

hashtag
Object Delivery

The ASV delivers supplies to other rescue vessels. The yellow vessel indicates clean water delivery. The black vessel indicates urgent medical kits (ball delivery).

hashtag
Yellow Vessels - Water Delivery

The ASV detects up to three (3) yellow boats that are anchored throughout the course with a black triangle shape fixed to both sides of the boat. The ASV locates the boats and delivers/shoots water at the black triangle shape. The ASV should strike (with a steady and visible stream of water) the black triangle shape for at least 3 seconds. Performance of the ASV's ability to correctly and intentionally aim water at the target will be evaluated and scored by the judges observing the scoring run.

hashtag
Black Vessels - Object Delivery

The ASV detects up to three (3) black boats that are anchored throughout the course, with a black plus-shape fixed to both sides of the boat. The ASV locates the black vessels and delivers a racquetball to the vessel, either striking the plus sign or inside of the vessel hull; or simply dropping the ball into the hull of the vessel is acceptable. Teams will not be penalized if the ball does not stay in the stationary vessel after successfully hitting the plus sign or inside of the hull. The ASV can be pre-loaded with up to three racquetballs before each scored run.

circle-info

A supply of racquetballs will be provided to each team at Team Check-in. As the racquetballs are used throughout the week, more will be available as they are recovered from the course.

hashtag
Capability Matrix

  • Core: Deliver water to orange vessel or ball to black vessel.

  • Advanced: Deliver water to orange vessel and ball to black vessel.

hashtag
Communications

The ASV reports on the following for this task:

  • Location and color of yellow / black stationary vessel

  • Type of delivery (water or ball)

Defined reporting guidelines are available in .

hashtag
Task Elements

Racquetballs are supplied from Amazon, .

Task Element
Description
Dimensions
Color

hashtag
3.2.5 Task 5 - Navigate the Marina

hashtag
Docking

The ASV must enter the marina and dock in an available slip (indicated by green color indicator). Each dock slip has a number sign: 1-3. The ASV must dock in the most desirable open dock, indicated by the lowest number available. For example, if dock #2 and #3 are available, the ASV should dock in #2 as the lowest number available.

Files to print the dock numbers can be found in .

circle-info

Note: there will not be a situation where a slip has a stationary vessel and a green indicator. However, there will be situations where a slip has a red indicator but does not have a stationary vessel.

hashtag
Capability Matrix

  • Core: Dock in any unoccupied bay.

  • Advanced: Dock in slip with green color indicator, signaling an available bay.

  • Disruptive: Dock in slip with green color indicator and the lowest number sign available.

hashtag
Communications

The ASV reports on the following for this task:

  • Dock identification (Dock N or S)

  • Slip number (Slip 1, 2, or 3)

Defined reporting guidelines are available in .

hashtag
Task Elements

Task Element
Description
Color
Dimensions

hashtag
3.2.6 Task 6 - Harbor Alert

hashtag
Sound Signal

The Harbor Alert task simulates an emergency maritime command-and-control, testing the ability of autonomous systems to detect, interpret and act on real-time dynamic cues that override other mission objectives, mirroring emergency maritime operations.

The ASV detects an audible signal and immediately abandons current task and:

  • One-Blast Signal = Navigate to emergency response zone (yellow buoy positioned at Task 3)

  • Two-Blast Signal = Return to marina (yellow buoy positioned at Task 5)

The sound signal can alert at any point during the mission. Each course will have a signal with a different frequency designated and published at the beginning of the day, the possible frequencies include: 600Hz, 800Hz, 1000Hz (+ 5%). The signal volume at distance:

  • 1m: 85-100 dB SPL

  • 60m: ~60 dB SPL

circle-info

Available for Download: The .wav files are available in the .

circle-info

hashtag
Hints

Choose an omni-directional microphone. If you are using a single microphone and it is pointing away from the sound signal source, then the signal may be difficult to detect.

Test your system in a noisy environment. Consider boat, waves, and wind noise.

hashtag
Capability Matrix

  • Core: Detect and classify audible signal (1 vs 2 blasts) and immediately abandon task, override behavior, and navigate safely to assigned zone/task.

  • Advanced: Report confirmation of signal and execute optimized routing and collision avoidance to assigned zone/task.

hashtag
Communications

The ASV reports on the following for this task:

  • Audible Alert Tone (1 or 2 blasts)

  • Frequency

  • Real-time status of response time

  • Assigned zone

Defined reporting guidelines are available in .

hashtag
3.2.7 Color Indicators

Custom color indicators will be used across the course. These color indicators are 3D-printed cylinders that are actuated to change the color between red and green. This single colored indicator is visible 360° radially on a horizontal plane only. It will be mounted on a custom buoy, roughly 18 in across at the base. More information will be released as this continues to be prototyped and tested. CAD files to print color indicators are available in .

Component Overview
Component
Description/Notes
Quantity per Unit
Vendor

hashtag
Color Indicator Buoy

The color indicators used throughout the course (with the exception of color indicators mounted to the dock for ) will be mounted on a custom buoy.

circle-info

The details in the following section are subject to change as the system is being developed. General size and shape will likely remain the same.

Color Indicator Buoy Components
Quantity

3.3 Communications Protocol

3.3.1 Message Format: Protocol Buffers (Protobuf)

3.3.2 Rules and Timing (required)

3.3.3 Transport

3.3.4 Minimal On‑wire Behavior (summary)

3.3.5 Resources Provided to Teams

3.3.6 Task Reporting Summary

3.3.7 Schema (report.proto)


This section defines how teams report ASV status from the team's Operator Control Station (OCS) to the RoboNation RoboCommand system during runs. During operations, teams are provided with a hard-wired connection (RJ-45) to the RoboCommand Network. This connection must be used to transmit all reports.

The course Ethernet connection is isolated:

  • Teams will not have Internet access through this connection

  • Teams will not be able to reach other external networks through this connection

hashtag
DHCP Addressing (IP Configuration)

  • Network: 10.10.10.0/24 (Subnet Mask: 255.255.255.0)

  • RoboCommand IP: 10.10.10.1

  • Team OCS IP assignment: Your computer will be automatically assigned an address in the 10.10.10.x range 10.10.10.100 through 10.10.10.200

hashtag
3.3.1 Message Format: Protocol Buffers (Protobuf)

Protocol Buffers is used to define message schemas and serialize data for transmission to RoboCommand. In simple terms:

  • Message fields are described in a human‑readable .proto file.

  • Team runs the compiler (protoc) to generate classes for your language (Python/C++/Go/etc.).

  • Team's code uses those classes to build and encode messages to a compact binary string.

Official docs:

circle-info

Click here to access the .

hashtag
3.3.2 Rules and Timing (required)

  • Format: Protocol Buffers

  • Timestamp: Every message must include a timestamp

  • Clock sync: Teams will be provided with a Network Time Protocol (NTP) source for system clock synchronization so timestamps align with field logs.

hashtag
3.3.3 Transport

  • Physical/network: Hard‑wired Ethernet from the OCS to the course network (RoboCommand)

  • Direction: Team to RoboCommand (reporting only)

  • Server: 10.10.10.1, Port: 50000 (TCP)

hashtag
3.3.4 Minimal On‑wire Behavior (summary)

  • When to send: On each required event/state change for a task, and otherwise at ≤5 Hz if a task specifies periodic updates.

  • What to send: Header(2 bytes) + Length(1 byte) + Payload(Length bytes) + Footer(2 bytes)

    • Header - ASCII "$R"

hashtag
3.3.5 Resources Provided to Teams

circle-info

RoboNation is actively working on this list, and there may be changes prior to competition.

To de‑risk adoption and ease debugging, RoboNation has published the following in :

hashtag
Onsite

  • Hardwire connection to the RoboCommand network provided in course operations tents.

  • Hardwire connection to a testing RoboCommand network in team village.

hashtag
Schema & Bindings

  • Canonical (versioned, current version shown in )

  • Pre‑generated for Python and C++

hashtag

  • Simple Client (Python): sends one (1) message over TCP (configurable)

  • Simple Client (C++): sends one (1) message over TCP (configurable)

  • Simple Server (Python): receives, decodes protobuf, prints to console for debugging

hashtag
3.3.6 Task Reporting Summary

hashtag
Task 1: Evacuation Route & Return - Entry & Exit Gates

The ASV reports on the following:

  • GatePass message (through second Entry Gate)

  • GatePass message (through second Exit Gate)

hashtag
Task 2: Debris Clearance - Navigation Channel

The ASV reports the following:

  • ObjectDetected message

hashtag
Task 3: Emergency Response Sprint - Speed Challenge

The ASV reports the following:

  • GatePass message (start of task)

  • ObjectDetected message

  • GatePass message (end of task)

hashtag
Task 4: Supply Drop - Object Delivery

The ASV reports the following (per stationary vessel):

  • ObjectDetected message

  • ObjectDelivery message

hashtag
Task 5: Navigate the Marina - Docking

The ASV reports the following:

  • Docking message

hashtag
Task 6: Harbor Alert - Sound Signal

The ASV reports the following:

  • SoundSignal message


hashtag
3.3.7 Schema (report.proto)

The following is the current version. Final field names and enums may be adjusted before the competition, but will be updated in .

3.1 Mandatory Activities

hashtag
3.1.1 Vehicle Transport Requirements

Teams must provide a cart to move the vehicle around the competition site and launch the vehicle into the water.

  • Cart must be manually propelled on site, no motorized carts.

  • Cart's handle must be solid, no rope or chain.

  • Cart’s width must be less than thirty-six (36) inches.

  • Carts are recommended to have six (6) inch (or more) diameter rubberized wheels.

  • Carts must be able to get wet with minimal impact to function.

  • Carts must be negatively buoyant in the water.

Suggested carts: garden cart, available at ; or dump cart, available at .

hashtag
3.1.2 Static Safety Inspection

Prior to deploying in the water, the ASV must meet all safety requirements. At a minimum, the following areas are checked:

  • Emergency Stop System (location of switches, on-board and remote functionality)

  • Demonstration of remote Emergency Stop failsafe functionality by removing the batteries or turning off the remote Emergency Stop transmitter.

  • Safety issues related to a propeller or hazard

More details on system requirements are available in

hashtag
3.1.3 Weight and Thrust Measurements

Vehicles are weighed at the start of every day of the competition. Teams transport the vehicle on their cart to the scale (similar to a veterinary scale, available at ) for weight measurement. The stable scale reading weight is recorded. Thrust is measured after the vehicle is deployed in the water either in manual or autonomous mode. The thrust value used is the highest scale reading that is stable for at least two seconds. Teams may opt to repeat their thrust measurement at each deployment.

During Finals runs, the vehicle must be re-weighed, and re-thrust tested every time it is launched into the water. If the vehicle stays in the water between finals runs, teams may forgo the weight and thrust test a second time. However, if a team is observed to be switching significant components or making modifications on their boat, the judges or TD staff may ask for a new measurement.

hashtag
Weight and Thrust Scoresheet

Parameters
Points

hashtag
Vehicle Weight Example Calculations

chevron-rightVehicle Weight: 60.5 lbshashtag

80 + (70 - 60.5) = 89.5 points

chevron-rightVehicle Weight: 113 lbshashtag

-250 - 5*(113 - 110) = -265 points

chevron-rightTwo Vehicles: #1) 87 lbs, #2) 50 lbshashtag

#1) 2*(110 – 87) = 46 points

#2) 80 + (70 - 50) = 100 points

Total Score: 46 + 100 = 146 points

Section 3: Autonomy Challenge

This section includes detailed requirements and instructions for the autonomy challenge portion of the competition.

These challenges showcase ASV performance through autonomous behaviors designed to represent research and real-world applications.

3.1 Mandatory Activities

3.2 Task Descriptions

3.3 Communications Protocol

  • Team ID List

3.4 Qualifying Round


3.5 Semi-Finals/Finals Round

Teams that qualify will have access to a full Semi-Finals Course once one becomes available. These courses consist of six (6) tasks: the mandatory navigation channel and tasks 2-6. Only one team may be on a Semi-Finals/Finals Course at a time. Note that teams may not know what course they are assigned until right before the start of their time slot.

During a Semi-Finals/Finals run the ASV must:

  • operate autonomously throughout the entire run; no remote-controlled survey runs allowed and teams must navigate directly back to the starting position with no deviations when resetting for another run.

  • enter the course through the gates in Task 1: Evacuation Route (Entry and Exit Gates).

transmit a heartbeat message to begin the run (as described in Section 3.3).

  • attempt the remaining Tasks 2-6 of their choice, in any order.

  • exit the course through the gates in Task 1: Evacuation Route (Entry and Exit Gates), at the end of the run.

  • The scoring criteria for Semi-Finals and Finals is detailed in Section 4: Scoring.

    Preliminary task Layout
    3.5 Semi-Finals/Finals Round
    Preliminary Course Layout

    18in

    Starboard Marker Buoy

    Taylor Made Sur-Mark Buoy

    950400

    Green

    39in

    (above waterline)

    18in

    20.3 cm

    Gate Buoy

    Polyform A-0

    A-0

    Green

    0.5 ft

    (above waterline)

    20.3 cm

    Obstacle Buoy

    Polyform A-0

    A-0

    Black

    0.5 ft

    (above waterline)

    20.3 cm

    Single Color Cylinder on custom buoy

    Custom built

    Red / Green

    1 ft (above waterline)

    18 in square

    Coroplast floating vessels

    Custom built

    Yellow / Black

    Full dimensions and plans can be found in

    36.8 cm

    Gate Buoy

    Polyform A-2

    A-2

    Green

    1 ft

    (above waterline)

    36.8 cm

    Single Color Cylinder on custom buoy

    Custom built

    Red / Green (color indicator) White with black diamonds (buoy)

    1 ft

    (above waterline)

    18 in square

    Obstacle Buoy

    Polyform A-2

    A-2

    Black

    1 ft

    (above waterline)

    36.8 cm

    Coroplast floating vessels

    Custom built

    Yellow / Black

    Full dimensions and plans can be found in

    Red

    Blue

    Orange

    24 inches x 24 inches

    Solid Color Cylinders

    Red / Green

    5.2 in. H x 5 in. W

    Coroplast floating vessels

    Yellow / Black

    Full dimensions and plans can be found in

    Green filament - Grass Green

    Green fins. PCTG filament from 3D Fuel

    1

    White filament - Brightest White

    Base and top. PCTG filament from 3D Fuel

    1

    Optional for powered testing

    Waterproof servo

    Pack of 4, need 1

    0.25

    Battery

    18650s. Pack of 6, need 2

    2

    Regulator

    5V 3A. Pack of 2, need 1

    0.5

    Needed for full system

    Battery Holder

    Pack of 10, need 2

    0.2

    041 ORing

    Pack of 20, need 1

    0.05

    8

    ¾ '' PVC Pipe - 4.5'' Long

    2

    ¾ '' PVC Pipe - 1.5'' Long

    4

    3'' Diameter Floats - 5.5'' Long

    8

    14'' Cable Ties

    8

    8'' Cable Ties

    16

    Port Marker Buoy

    Taylor Made Sur-Mark Buoy

    950410

    Red

    Gate Buoy

    Polyform A-0

    A-0

    Classic Red

    Gate Buoy

    Polyform A-2

    A-2

    Classic Red

    Stationary Vessels

    Coroplast floating vessels

    Full dimensions and plans can be found in Data Sharingarrow-up-right

    Yellow / Black

    Racquetballs

    FJBM Squash Ball

    Floating Dock

    Large dock cube Item Code: C000000008

    Beige

    Dock: 40 in. W x 10 ft. L x 16 in. H

    Tines: 4-7 ft. L

    Individual Cube: 20 in. x 20 in. x 16 in. H Two dock piers with three (3) docking slips

    Number Banners

    Vinyl Banner

    Needed for manual testing

    Red filament - Fire Engine Red

    Red fins. PCTG filament from 3D Fuel

    1

    3D Fuelarrow-up-right

    ¾ '' PVC Elbows

    8

    ¾ '' PVC Tees

    6

    ¾ '' PVC Pipe - 12'' Long

    4

    Semi-Finals/Finals Round
    Section 3.3: Communications Protocol
    www.taylormadeproducts.comarrow-up-right
    color indicator buoys
    Section 3.3: Communications Protocol
    shop.polyform.comarrow-up-right
    Section 3.3: Communications Protocol
    shop.polyform.comarrow-up-right
    Section 3.3: Communications Protocol
    www.amazon.comarrow-up-right
    RoboNation Data Sharingarrow-up-right
    Section 3.3: Communications Protocol
    RoboBoat Data Sharing folderarrow-up-right
    Section 3.3: Communications Protocol
    RoboNation Data Sharingarrow-up-right
    Task 5
    Entry/Exit Gates
    Navigation Channel
    Navigation Channel
    Speed Challenge
    Speed Challenge
    Examples of Delivery Boats
    Dimensions for Delivery Boats
    Navigate the Marina: Docking
    Color Indicator that changes from green to red using a servo before the start of the run
    NOTE: Color indicator will be red OR green
    Rendering of Color Indicator on the buoy (color will be red OR green)
    All dimensions are in inches. Small rectangular holes in the board are to attach coroplast to buoy frame using cable ties. They are 0.4'' x 0.2'' in this depiction.
    PVC Color Indicator Buoy Frame using 3/4'' PVC pipes and fittings.

    39in

    (above waterline)

    0.5 ft

    (above waterline)

    1 ft

    (above waterline)

    5.5 cm diameter

    Black

    ¾ '' PVC Pipe - 7'' Long

    NTP Server: 10.10.10.1
  • Protocol/Port: NTP (UDP 123)

  • Heartbeat message: Teams send a heartbeat message at 1 Hz.

  • Rate limit: ≤ 5 Hz (no more than five messages per second per ASV/report stream) unless otherwise specified. This rate is subject to change.

  • Length - Payload length (1 byte, unsigned)

  • Payload - Serialized task‑appropriate message type from report.proto with required fields populated (timestamp, positions/IDs/colors as applicable).

  • Footer - ASCII "!!"

  • https://protobuf.dev/arrow-up-right
    Team ID List
    GitHubarrow-up-right
    report.proto arrow-up-right
    bindingsarrow-up-right
    Examplesarrow-up-right
    GitHubarrow-up-right
    3.3.7 Schema (report.proto)
    All components are properly secured
  • Towing points and tow harness is present and secure

  • 80 + (70 - w)

    Dimensions greater than:

    - three feet of width or

    - three feet of height

    - six feet of length

    Disqualified!!!

    Thrust (t) vs weight (w)

    100*(t / w)

    ASV weight > 140 lbs.

    Disqualified!!!

    140 lbs > ASV weight > 110

    -250 - 5*(w - 110)

    110 lbs > ASV weight > 70

    2*(110 – w)

    homedepot.comarrow-up-right
    homedepot.comarrow-up-right
    Section 5.3: Vehicle Requirements.
    scaleline.comarrow-up-right
    Example Vehicle Carts
    Thrust Measurement

    ASV weight ≤ 70 lbs

    Color Indicator
    Stationary Vessels
    Data Sharingarrow-up-right
    Color Indicator Buoy
    Stationary Vessels
    Data Sharingarrow-up-right
    Color Indicators
    Stationary Vessels
    Data Sharingarrow-up-right
    3D Fuelarrow-up-right
    3D Fuelarrow-up-right
    Amazonarrow-up-right
    Amazonarrow-up-right
    Amazonarrow-up-right
    Amazonarrow-up-right
    Amazonarrow-up-right
    https://github.com/robonation/robocommand/blob/main/proto/report.proto
    edition = "2024";
    package robocommand.roboboat.v1;
    import "google/protobuf/timestamp.proto";
    
    enum RobotState {
       STATE_UNKNOWN = 0; 
       STATE_KILLED = 1; 
       STATE_MANUAL = 2; 
       STATE_AUTO = 3; 
    }
    
    enum TaskType { 
       TASK_UNKNOWN = 0;
       TASK_NONE = 1; 
       TASK_ENTRY_EXIT = 2; 
       TASK_NAV_CHANNEL = 3; 
       TASK_SPEED_CHALLENGE = 4; 
       TASK_OBJECT_DELIVERY = 5; 
       TASK_DOCKING = 6; 
       TASK_SOUND_SIGNAL = 7; 
    }
    
    enum ObjectType { 
       OBJECT_UNKNOWN = 0; 
       OBJECT_BOAT = 1; 
       OBJECT_LIGHT_BEACON = 2; 
       OBJECT_BUOY = 3; 
    }
    
    enum Color { 
       COLOR_UNKNOWN = 0; 
       COLOR_YELLOW = 1; 
       COLOR_BLACK = 2; 
       COLOR_RED = 3; 
       COLOR_GREEN = 4; 
    }
    
    enum GateType { 
       GATE_UNKNOWN = 0; 
       GATE_ENTRY = 1; 
       GATE_EXIT = 2; 
       GATE_SPEED_START = 3; 
       GATE_SPEED_END = 4;
    }
    
    enum SignalType { 
       SIGNAL_UNKNOWN = 0; 
       SIGNAL_ONE_BLAST = 1; 
       SIGNAL_TWO_BLAST = 2; 
    }
    
    enum DeliveryType { 
       DELIVERY_UNKNOWN = 0; 
       DELIVERY_WATER = 1; 
       DELIVERY_BALL = 2; 
    }
    
    enum PatrolBoatActionType {
      PATROL_BOAT_ACTION_UNKNOWN = 0;
      PATROL_BOAT_ACTION_STOPPING = 1;
      PATROL_BOAT_ACTION_RESUMING = 2;
    }
    
    /**
     * Report is the only message sent to the RoboCommand server
     * Report message contains:
     * team_id: unique team identifier (i.e. RNRB, provided in Team Handbook)
     * vehicle_id: unique vehicle identifier (i.e. S1, S2, where "S" signals Surface Vessel)
     * seq: monotonically increasing sequence count
     * sent_at: timestamp of message transmission
     * body: one of the listed body messages
     */
    message Report {
      string team_id = 1;
      string vehicle_id = 2;
      uint32 seq = 3;
      google.protobuf.Timestamp sent_at = 4;
    
      oneof body {
        Heartbeat heartbeat = 10;
        ObjectDetected object_detected = 11;
        GatePass gate_pass = 12;
        ObjectDelivery object_delivery = 13;
        Docking docking = 14;
        SoundSignal sound_signal = 15;
        PatrolBoat patrol_boat = 16;
      }
    }
    
    /**
     * Latitude and Longitude in decimal degrees.
     * Latitude in the range -90.0 to +90.0
     * Longitude in the range -180.0 to +180.0
     */
    message LatLng {
      double latitude = 1;   
      double longitude = 2;  
    }
    
    /**
     * Heartbeat message contains:
     * RobotState: state of the ASV
     * position: lat, lng position of ASV
     * spd_mps: speed of AVS in m/s
     * heading_deg: compass heading in degrees of ASV: North = 0, East = 90
     * current_task: task the ASV is currently on
     */
    message Heartbeat {
      RobotState state = 1;
      LatLng position = 2;       
      float spd_mps = 3;
      float heading_deg = 4;     
      TaskType current_task = 5; 
    }
    
    /**
     * Tasks 2, 3 & 4
     * Object detected message contains:
     * object_type: type of the object
     * color: color of the object
     * position: lat, lng position of object
     * object_id: team-scoped stable ID
     * task_context: type of task
     */
    message ObjectDetected {       
      ObjectType object_type = 1;  
      Color color = 2;             
      LatLng position = 3;
      uint32 object_id = 4;
      TaskType task_context = 5;
    }
    
    /**
     * Tasks 1 & 3
     * Gate pass message contains:
     * type: type of gate
     * position: lat, lng position of ASV
     */
    message GatePass {
      GateType type = 1;
      LatLng position = 2;
    }
    
    /**
     * Task 4
     * Object delivery message contains:
     * vessel_color: color of the vessel
     * position: lat, lng position of ASV
     * delivery_type: WATER or BALL
    */
    message ObjectDelivery {
      Color vessel_color = 1;
      LatLng position = 2;
      DeliveryType delivery_type = 3;
    }
    
    /**
     * Task 5
     * Docking message contains:
     * dock: dock identifier - North(‘N’) or South(‘S’)
     * slip: slip number - ‘1’, ‘2’, or ‘3’ 
     */
    message Docking {
      string dock = 1;
      string slip = 2;
    }
    
    /**
     * Task 6
     * Sound signal message contains:
     * signal_type: type of signal detected - one or two blasts
     * frequency_hz: nominal frequency of detected blast - 600, 800, or 1000
     * assigned_task: task assigned by signal_type
     */
    message SoundSignal {
      SignalType signal_type = 1;
      uint32 frequency_hz = 2;
      TaskType assigned_task = 3;
    }
    
    /**
     * Patrol Boat
     * patrol_boat_action_type: What action the team ASV is performing in response to the patrol boat
     */
    message PatrolBoat {
      PatrolBoatActionType patrol_boat_action_type = 1;
    }