Unit 13: OOP & Inheritance

Structure competition code with encapsulation, inheritance, and composition so mechanisms can be reused and hardware changes stay contained.

Advanced

10Lessons

0Completed

Not StartedCurrent Status

Resume 13.1 · EncapsulationOpen Dashboard

Lesson Roadmap

13.113.1 · EncapsulationLesson 13.1: Encapsulating Component Logic into Mechanism ClassesOpen13.213.2 · InheritanceLesson 13.2: Extending Parent Classes for Modular Hardware SubsystemsOpen13.313.3 · @OverrideLesson 13.3: Overriding Behavior with @Override for Custom ImplementationsOpen13.413.4 · Static ConstantsLesson 13.4: Managing Shared Constants with the static KeywordOpen13.513.5 · Robot ClassLesson 13.5: Architecting a Modular Robot Class with Nested SubsystemsOpen13.613.6 · Build IntakeLesson 13.6: Build RobotConfig.java and Intake.javaOpen13.713.7 · Build LiftLesson 13.7: Build MotorMechanism.java and Lift.javaOpen13.813.8 · Build RobotHardwareLesson 13.8: Build RobotHardware.javaOpen13.913.9 · Complete TeleOpLesson 13.9: Complete CompetitionTeleOp.javaOpenCCUnit 13 · Coding ChallengeUnit 13 Comprehensive Coding Challenge: Modular Robot ArchitectureOpen

What This Unit Covers

Encapsulate mechanism hardware and logic into private-member classes with clean public interfaces, eliminating duplicated code across OpModes.

Apply inheritance and @Override to build a family of specialized mechanisms from a shared parent, with the compiler enforcing correct implementation.

Build Intake, Lift, RobotHardware, and CompetitionTeleOp as a reusable multi-file project for TeleOp and autonomous.

Review the sequence and goals here, then resume at your first incomplete lesson.

Already know this unit?

Complete the comprehensive coding challenge to prove every unit objective and jump directly to Unit 14: Computer Vision.

Take the Coding Challenge →

Stuck on this lesson?

Ask about anything on this page. It can see which lesson you have open and which part you are reading.