A key part of robotics is programming is learning the java code language, creating pseudocode based on game strategy, and create programming for autonomous and driver controlled periods
We implemented software in our Robot using Java programming language with a strategy to complete the missions and score points. We developed a design/algorithm as a pseudo code to follow the rules and requirements defined in the First competition rule guide. Once the pseudo code is developed, we work on theĀ
As a team, we spent time in planning and developing the robot's physical and logical design. Building the robot's hardware first gave us a clear understanding of its dimensions, motor placement, and sensor locations. Knowing exactly how the mechanical parts interacted allowed us to map out how the software needed to control them.
To transition from a physical robot to a working Java program, we followed a structured design process:
Component Mapping: We mapped every motor, servo, and sensor on the robot to specific ports on the control hub. This became the foundation for our Java hardware configuration (Hardware Map).
Pseudo-coding: We wrote downout the robot's logic in plain English before translating it into code. For example, we planned steps like: "If the camera detects the April tag pattern that indicates that the cell assembly is not ready to shoot the balls, stop the drivetrain and park the robot."
Defining Movement Logic: We decided how the robot should move during both the Autonomous and Driver-Controlled (TeleOp) periods. This included deciding how the joysticks on the controller would map to the wheels for smooth steering.
This design phase was essential. By solving mechanical and logical challenges on paper first, we avoided major bugs and saved hours of troubleshooting once we began writing the actual Java program.
This year all of our sister teams collaborated on the same code so we could be more efficient....