Grading and tasks

Designs must be reviewed and approved by instructors before fabricating mechanical parts or before PCBs are ordered.

Designs can be submitted for review at any time.

Design project access must be granted to instructors for review purposes.

Mechanical design must be created with Fusion 360.

Code must be reviewed and approved by instructors to complete the tasks and to qualify for competitions.

Short description about the daily progress and the time spent.

Daily blog should describe what you did and what was the result of it.

Days without any activity do not need to be blogged about.

Example:

In Delta room 2024.

Mondays 18:15 - 19:00, once every two weeks.

5 minutes per team.

At least 1 team member presents the progress of all team members.

Slides must be prepared and used to illustrate the progress.

Code running on robot’s PC.

Robot moves at least 1 meter on the court.

30 seconds per attempt.

Robot starts from the center of the court, facing its own basket.

1 ball on the opposing half of the court.

60 seconds per attempt.

Task is completed when the ball is in the middle of the camera’s horizontal field of view and the robot is not moving.

Robot starts from its corner of the court.

1 ball on the opposing half of the court.

Robot must stop if the ball is closer than 10 centimetres.

Instructor will move the ball when the robot gets closer than 10 centimetres to the ball.

Robot must follow the ball by simultaneously rotating and moving towards it.

Robot must use omnidirectional motion.

Task is completed when the robot is able to follow the ball.

Robot starts from its corner of the court.

60 seconds per attempt.

1 ball is placed by an instructor.

Task is completed when:

Robot starts from its corner of the court.

60 seconds per attempt.

1 ball is placed by an instructor.

Task is completed when the ball is thrown at least 1 meter towards the opponent’s backboard.

Refer to the robot basketball manager documentation.

Robot ID can be changed.

Robot reacts to referee signals that are targeted to it:

Robot correctly uses basket color from the signal’s info.

Robot retries to connect to basketball manager if connection is lost or has not been established yet.

Robot starts from its corner of the court.

60 seconds per attempt.

11 balls on the court.

Task is completed when a ball is thrown into the opponent’s basket.

Robot starts from its corner of the court.

Balls are placed according to basketball rules.

At least 3 points must be scored.

60 seconds per attempt.

Robot starts from its corner of the court.

Balls are placed according to basketball rules.

At least 5 points must be scored.

60 seconds per attempt.

5 balls inside the playing court.

6 balls outside the playing court.

Balls are placed by instructors.

Robot’s starting position will be selected by the instructors.

At least 2 points must be scored.

60 seconds per attempt.

60 seconds per attempt.

1 ball on the court placed behind the opponent robot.

Both robots are placed by the instructors.

When the robot finds the ball behind the opponent robot, the opponent robot moves between basket and the ball and remains there.

Task is completed when the ball is scored.

Keyboard or gamepad or similar controller.

Robot game logic can be started and stopped.

Robot can be moved manually.

Robot starts from its corner of the court.

60 seconds per attempt.

One ball at 10 centimetres from the opponent’s basket.

Another ball at the other corner of the backcourt.

Ball must be thrown from where it is located.

Task is completed when both balls are thrown into the opponent’s basket.

Robot starts from its corner of the court.

60 seconds per attempt.

1 ball is placed by an instructor at the backcourt.

Robot must grab the ball and move to the frontcourt.

Ball can only be moved by holding it.

Only 1 throw from the frontcourt is allowed.

Task is completed when the ball is scored from the frontcourt.

Thrower should technically be able to throw the ball.

CAM approved.

Parts fabricated.

Thrower assembled and attached to the robot.

Design approved.

Wheels must be attachable to the motors.

Design approved

Motors and wheels added to the assembly

Design approved.

Camera added to the assembly.

Field of view pyramid added to the camera.

Thrower attached to the chassis in the design.

Thrower should technically be able to throw the ball.

Throwing angle can be adjusted through the mainboard (for example with a servo).

Thrower designed to grab a ball, hold the ball while moving and release or throw the ball while holding.

Chassis for connecting all the parts.

Battery mounts.

Electronics mounting:

Design that prevents balls from getting stuck against the robot. If the robot drives against the ball, the ball should roll away.

CAM approved:

All parts fabricated.

Do not need to be assembled.

All mechanical parts attached together.

No adhesives used.

Motor and ESC attached and working.

Motor speed can be controlled through mainboard.

Design approved.

Required functionality:

Design approved.

Can be combined with the mainboard.

Requirements:

Motors can be controlled through the mainboard.

Can be controlled through a mainboard.

Motors can be rotated in both directions.

Encoders must work. Closed loop (e.g. PI or PID) speed control must work.

Implements required functionality.

Code hosted on GitHub in team’s repository.

Code reviewed and approved.

All documentation must be in your team’s repository with electronics design files.

Functionality and connector pinouts described in AsciiDoc format in electronics/README.asciidoc file.

Schematic PDF file.

Components BOM in TSV (tab-separated values, *.tsv) format.

Gerber files in separate directory.

Same requirements as for "Mainboard documented" task.

Commands can be sent to the mainboard to change the thrower angle.

Commands can be sent to the mainboard to grab, hold and release or/and throw a ball.

Voltage regulator is connected and working between battery and thrower motor controller to ensure that changing battery voltage doesn’t affect thrower motor speed.

Attached to the robot.

Command(s) can be sent through mainboard:

Power buttons and power path control board works.

Mechanics assembled:

Electronics attached and working:

In team’s GitHub repository documentation branch and README.asciidoc file.

In English.

Names of the team members.

Public Fusion 360 project link.

Progress blog section.

Either old robot or new robot qualifies according to basketball rules:

New robot qualifies according to basketball rules.

Test robot not allowed.

Bonus points for the best team among course participants.

Bonus points for the 2nd best team among course participants.

Bonus points for the 3rd best team among course participants.

Refer to Team documentation requirements

Must be reviewed and approved by instructors.

No grades if not completed.

10 minutes per team.

Overview of the robot.

Talk about your experience.

No grades if not completed.

Return parts, but keep robots assembled.

No grades if parts are not returned.

Refer to Handed out equipment