How blackfrogsftc6134/into_the_deep_worlds works
Project type and purpose
• This is an Android-based robot control system (the FTC Robot Controller) plus accompanying user code (TeamCode) and a small Java test harness (MeepMeepTesting). It’s a full-stack mobile control application that runs on an Android device (phone or Control Hub), communicates with a Driver Station over Wi-Fi Direct, and drives hardware modules (Expansion Hubs, sensors, motors) via USB/FTDI and I²C.
File structure
• Top-level modules (defined in settings.gradle):
• FtcRobotController – the Android app (src/main/java/org/firstinspires/ftc/robotcontroller…, AndroidManifest.xml, res/)
• TeamCode – the team’s Java OpModes and libraries (src/main/java/org/firstinspires/ftc/teamcode…)
• MeepMeepTesting – a standalone Java test (src/main/java/com/example/meepmeeptesting)
• Build scripts: root build.gradle, build.common.gradle, build.dependencies.gradle, Gradle wrapper under gradle/, settings.gradle.
• .github contains CI/contribution templates.
• doc/ and libs/ hold legal docs, media, and keystores.
README for additional insights
• Confirms that FtcRobotController builds an Android app to control an FTC robot.
• Explains OpMode samples in external/samples and user code in TeamCode.
• Lists dependencies (Android Studio Ladybug, Java 1.8) and external docs (Blocks, OnBot Java, Javadoc, online tutorials).
Main components
a. Android Device (Robot Controller)
• Presentation/UI Layer
• FtcRobotControllerActivity (layouts in res/layout, menus in res/menu)
• Web server for Blocks/OnBot Java (via WebHandlerRegistrar)
• OpMode Framework
• FtcOpModeRegister, OpModeManager, LinearOpMode/OpMode base classes
• Annotation processor (OpModeAnnotationProcessor.jar) to register TeamCode classes
• Hardware Abstraction Layer
• HardwareMap (DigitalChannel, DcMotor, Servo, IMU, etc.)
• Device interface modules (LegacyModule, ModernRoboticsUsbDeviceInterfaceModule)
• Low-Level Drivers
• USB/FTDI layer (Robocol socket, ReadWriteRunnable)
• I²C (I2cDeviceSynch)
• Resources & Config
• res/xml device_filter, app_settings, teamwebcamcalibrations
• External Libraries
• OpenCV/EasyOpenCV, AprilTag, TensorFlow (for vision processors)
b. TeamCode Module (User OpModes)
• Drive/trajectory libraries (SampleMecanumDrive, SampleTankDrive)
• Subsystems (ArmMech, Claw, Pivot, etc.)
• Opmode definitions (iterative & linear) under drive/opmode, opmode, test, trajectorysequence
c. MeepMeepTesting
• Simple Java program (MeepMeepTesting.java) for off-device testing
d. Build & CI
• Gradle Wrapper → resolves dependencies → compiles modules into APKs
• GitHub Actions/triggers via .github templates for PRs and contributions
Relationships and interactions
• Driver Station App ←Wi-Fi Direct→ Robot Controller App (Robocol/TCP)
• Robot Controller App ←USB/FTDI & I²C→ Expansion Hubs, Control Hub, sensors, motors
• TeamCode classes → loaded at runtime by OpModeManager inside Robot Controller
• Blocks/OnBot Java front-end (browser) ←HTTP→ Robot Controller embedded server
• Gradle build → outputs Robot Controller APK + TeamCode library → deployed to Android device
Architectural patterns & design principles
• Android MVC/MVP: Activities (View/Controller), resource layouts (View), HW abstraction (Model)
• Plugin/Annotation-scanning: user OpModes are automatically discovered and registered
• Layered design: Presentation → Control Framework → Hardware Abstraction → Drivers → OS
• Modularity: separate Gradle modules for core SDK (FtcRobotController), user code (TeamCode), tests
Technologies & frameworks
• Java 1.8, Android SDK Ladybug
• Gradle build system
• FTDI/USB drivers, I²C device sync
• OpenCV, EasyOpenCV, AprilTag, TensorFlow Lite
• Android WebView/HTTP server for Blocks & OnBot Java
• JUnit (if present in MeepMeepTesting)