From 0b2a6e330effe1cd7e1a2a1acd88207793c32dd2 Mon Sep 17 00:00:00 2001 From: Westside Robotics Date: Wed, 4 Jan 2023 14:51:24 -0800 Subject: [PATCH] 1-4-2023 update 1 link --- AprilTags-for-FTC-Blocks.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/AprilTags-for-FTC-Blocks.md b/AprilTags-for-FTC-Blocks.md index 8f9a00c..d3c02c5 100644 --- a/AprilTags-for-FTC-Blocks.md +++ b/AprilTags-for-FTC-Blocks.md @@ -1,4 +1,3 @@ -# AprilTags for FTC Blocks ## Introduction @@ -268,7 +267,7 @@ Still in the open white workspace, pull out another myBlock called `startAprilTa

[[/images/AprilTags-for-FTC-Blocks/535-startDetector.png]]

-This myBlock uses a default **camera resolution** of 640 x 480 pixels. The values here must be **supported by your camera** and [**adequate**](https://github.com/WestsideRobotics/AprilTags-for-FTC-Blocks/wiki#Field-Testing) for detecting your AprilTag on the Signal Sleeve at the intended distance. +This myBlock uses a default **camera resolution** of 640 x 480 pixels. The values here must be **supported by your camera** and [**adequate**](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/AprilTags-for-FTC-Blocks#field-testing) for detecting your AprilTag on the Signal Sleeve at the intended distance. If the values aren't supported, your OpMode will give an error message that should list the actual resolutions supported by your webcam or phone camera: