Add Limelight3A support and AprilTag telemetry in MainTeleOp #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Description
LLResult,LLResultTypes, andLimelight3Aand a privateLimelight3A limelightfield inMainTeleOp.onStartButtonPressed()withhardwareMap.get(Limelight3A.class, "limelight"), callpipelineSwitch(0), andstart().gamepad1.a()so on press it callsLLResult result = limelight.getLatestResult(), checksresult != null && result.isValid() && !result.getFiducialResults().isEmpty(), and logs the first fiducial'sgetFiducialId()viatelemetry.addData("AprilTag ID", id)followed bytelemetry.update().limelight.stop()(guarded by a null check) to end Limelight polling.Testing
TeamCode/src/main/java/org/firstinspires/ftc/teamcode/MainTeleOp.java.Codex Task