what? 😂

The cycling speed was amazing. After seeing that, my brain is shaken, physically and figuratively (I got a concussion while watching it.) It is truly amazing. When the cones are picked up and fall down so quickly, it reminds me of my own life. This is truly one of the robots of all time. Thank you so much to HOW 14469 for inspiring me.

@@austinsus13194A ​ you got something against their team? The robot is impressive

???

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

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

Yes, we are.

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

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.

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);

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.

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.

Yes, we are.

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.