You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Limelight connected to Asteria Deluxe publishes the coordinates of detected targets in relation to the crosshair in the middle of the Limelight.
Therefore, we can write code that will direct the robot to turn to face the target.
The function should live in the Drivetrain object, and be called by holding a button on the driver's controller.
When the 'x' value published to NetworkTables is above a certain value, the robot should turn in a direction. When it is below a certain value, it should turn the other. When it is between the values, the robot should not turn, but instead move forward or backwards at the rate of the throttle.
For extra credit, try making the rate of turning be controlled by the rate of the throttle application.
The text was updated successfully, but these errors were encountered:
Yesterday we implemented a bang-bang algorithm, using the same general method as 2017 Robot Code.
The constants used should be moved into c.java
Feature requests:
-Proportional rather than bang-bang control
-Move forward when the robot is on center
-Move forward/(backward?) proportional to throttle when robot is on center
-Print an error or light an indicator on the robot dashboard when the button is pressed but there is no target in view
The Limelight connected to Asteria Deluxe publishes the coordinates of detected targets in relation to the crosshair in the middle of the Limelight.
Therefore, we can write code that will direct the robot to turn to face the target.
The function should live in the Drivetrain object, and be called by holding a button on the driver's controller.
When the 'x' value published to NetworkTables is above a certain value, the robot should turn in a direction. When it is below a certain value, it should turn the other. When it is between the values, the robot should not turn, but instead move forward or backwards at the rate of the throttle.
For extra credit, try making the rate of turning be controlled by the rate of the throttle application.
The text was updated successfully, but these errors were encountered: