1) Take a look at Sprint 2’s video. We use a pixel pusher to move the purple pixel onto a spike mark. 2) We can’t control where a collected pixel goes but we do know which color is on which side with the color LEDs

Congratulations!! Well deserved.

We use our color sensors on our smart bucket to detect the pixel color. We have two REV Blinkin, and they are correspondent to the sensor on the appropriate side. So the right sensor aligns with the right LED, and so does the left.

Thank you@@HowRobotics

We do not utilize Road Runner during autonomous. We utilize a home grown motion planning library that allows a programmer to navigate a robot using either vision with April Tags or dead reckoning with drive wheel encoders.

We had a cover on the back of the robot.

For our AndyMark Entrapption Stars, we only cut off every other wing leaving 5 wings. Other than that there aren't any other changes to the Entrapption Stars.

@@HowRobotics thank you verry much

As in the black 3D printed part? That’s the intake.

We’re using a 720p webcam.

We’re not sure we understand your question. Are you asking about the motor that operates the linear actuator or the arm itself? In either case, it highly depends on the load you’re planning to put on it and that varies from robot to robot.

The structure of the intake is 3d printed, and we used Entrapption stars (Red wheels) as the wheels for the intake. We used gobilda servos for the rotation of the wheels and for the movement of the gates.

All the best to your team this season! Congratulations on having a great meet 2 last week. It’s a rebuilding year for us… lots of challenges and lots to learn. Definitely hope to see you guys at state too.

If you're talking about the X-shaped piece, it is called a 1610 Series Face Thru-Hole Pillow Block (10mm Bore), if you are talking about the little block piece at the end, it is called a 1203 Series Block Mount (1-1).

Link to the block mount: www.gobilda.com/1203-series-block-mount-1-1-4-pack/ Link to the pillow block: www.gobilda.com/10mm-bore-face-thru-hole-pillow-block-32mm-x-40mm-mounting-pattern/?gclid=Cj0KCQiAyKurBhD5ARIsALamXaHTHN3SxV6rqzb0GoFnQv8TwE62xIuymarn4eLU7Owjmvl6gOUAJ-YaAiVwEALw_wcB

@@HowRobotics I was taking about the block mount, thank you very much!

For motion control, we are using a PID with feedback from the built-in IMU’s gyro and two drive wheel encoders

Yes, if you go the the GoBilda website and find the Super Duty Worm Drive Pan Kit (28:1 Ratio) and scroll down, you can find a STEP file in the downloads section. Link: www.gobilda.com/super-duty-worm-drive-pan-kit-28-1-ratio/

HIOUOUIUOUUUUUUUUUNPO;'GF696DE6

Thanks! We would have loved to. Doesn’t always work out unfortunately. Maybe next year.

@@HowRobotics Good luck next season, are you guys applying for MTI? would love to see you guys there.

No, we won’t be applying to MTI. Best of luck at the tournament. You guys have an awesome robot!

Hey there, it seems like this question has been asked before in this video. Take a look at the answer. If there’s something more specific you’d like to find out, let us know.

For our rotating turret, we are using a worm-gear system and mounted the circular plate on top of it. The turret by itself can rotate 360 degrees, but due to having a huge delivery mechanism mounted and wired, it is limiting the rotating turret from spinning to its full capacity, so we ended up stopping it with encoders. our turret goes up to 135 degrees left and right when the claw is faced towards the front. Our slides for our vertical and horizontal extension are heavy, but the rotating plate is fine. Some concerns for turret based robots that have to reach high heights is the weight imbalance, which can be countered with weights in the robot in order to displace the center of gravity. Let me know if you have any more questions or if any of these were unclear.

For our 3d design we used Onshape.

Yes, we are.

Yes, we are.

I believe it is a thick silicon rubber band. We bought it from Amazon.

To even compete and qualify for Worlds will require us to make it to the state championship first. We’re not even thinking that far ahead to be honest. First things first, we will need to qualify for the state competition from the upcoming Feb 4 league championship.

We are using a GoBilda 5.2:1 ratio motor which is 1150 rpm.

For the vertical GoBilda viper slides we are using two 13.7:1 435 rpm motors. For the horizontal cascading x-rail we are using one 20:1 neverest motor.

The horizontally extending arm is a cascading x-rail slide kit we got a while back from ServoCity. The model we are using right now is discontinued, so an alternative slide kit could be the 4-stage Viper Slides from GoBilda.

Hey there! Our CAD is done through OnShape since there is a large library of FTC parts available on it. These parts are then imported into Inventor where they are constrained together to make our robot. All the CAD in this video is done and displayed on Inventor. Thank you for the question!

Well the first step, something that I messed up in, is to make sure that you are using the same rpm motor on both sides. Another thing to try is to run each side separately and see where you can see a clear difference. Maybe some of the rails weren’t built properly, or something is getting caught in one of the rails. Also make sure to constantly check your strings for any rubbing or catching. Next, check your program to make sure both are moving at the same power and speed. One thing to consider is to mechanically attach both sides of the rails with one or two straight bars. This will keep the rails together for sure, but try fixing it with the previous fixes. If you try this fix with the problem still there, it could ruin the rails. Let me know if this works.

In addition to the reply above, one of the biggest issues with moving the rails simultaneously is string tension. The tension has to be equal on both sides. Strings often get stretched with continued usage, which can cause the rails to become uneven after awhile. Connecting a bar between the rails can help you visually since you could tighten the strings until the bar becomes even while running both rails.

@@HowRobotics we were able to get both slides to run at the same speed, but one is going up while the other is going down and vice versa. May I see the driver control code for your slides? The problem is the code using the encoders

@@GeneticDigGaming You might have a problem with the position, and the solution is to move in the opposite direction. However, you cannot reverse the direction of the motor if you are using RUN_TO_POSITION. This will not work since it is using position. To solve this, just give the rail that is going in the opposite direction a negative position. This will allow the motor to turn in the opposite direction since it is trying to get to that negative position. Here is an example of what I mean: RailRight.setTargetPosition(position); RailRight.setMode(DcMotor.RunMode.RUN_TO_POSITION); RailRight.setPower(1); RailLeft.setTargetPosition(-position); RailLeft.setMode(DcMotor.RunMode.RUN_TO_POSITION); RailLeft.setPower(1);