Tomorrow is my VEX Competition and I just now found out that we have almost nothing correct. First of all, we did not understand the autonomous period and we have no code for it. So I was wondering if anyone had a VEX V5 code I could borrow and then I can just put sensors on my robot where it will be needed for the code. I HAVE NO IDEA HOW TO CODE SOMETHING IN LESS THEN A DAY!!!
Secondly, (which I can’t believe we missed), we do not have a second robot for our competition. I was told that another group will bring a robot they built and designed and together we would be an alliance. Now I’m a little confused because I went and googled whether or not we needed 2 robots and unfortunately it says we need to make our own robot for our OWN alliance.
Any ideas? I know you guys are probably thinking that i should have just read the Over Under Manuel better, but we had a scheduling issue, and did not get started until about 3 weeks ago. Some of you guys are really good at this stuff and could’ve built a robot in just a day that could be able to compete in this Competition, but I’m here begging, and i mean BEGGING for you to give me some help. Im a total beginner in this.
I totally get it. Last year was my first year and it can be scary going to your first comp. Auton code is not required if you don’t have the time for it. My first few comps last year we didn’t have an auton and we did fine. The only downside to not having an auton is not being able to get win point. During the auton period your robot will just sit there and that is totally ok!
With the other question on having to build another robot I think you were mislead on this rule. Every team will compete with one robot and it seems like you have one and that is perfect! During qualifying matches you will be randomly paired with other teams, one on your team and two against you. In total there will be four different teams competing.
You’re doing great! You’ll have lots of fun at your comp and I’m sure you’ll do great!
It basically moves the robot forward and spins the intake in reverse to score the triball
//MOVES ROBOT FORWARD
RightbackMotor.startRotateFor (forward, 30 ,degrees);
RightfrontMotor.rotateFor (forward, 30 ,degrees);
LeftbackMotor.rotateFor (forward, 30 ,degrees);
LeftfrontMotor.rotateFor (forward, 30 ,degrees);
I remember at one of my first comps, another team asked us if we used screws on our robot. My biggest piece of advice is to try to learn from other teams, ask around. I can almost guarantee that there will be somebody who will be happy to help.
But I need to know about how many millimeters my robot needs to move forward to get toward to triball, and if the starting position I start in is too far to the right or left, then the whole code is ruined. Then I have to pick up the triball and code a bunch more for turning around and how many more millimeters I need to move backwards.
Seems like tuning would definitely help, and maybe you should look into a line-up tool for auton. Just grab some c-channels and screw them together at an angle or something so that you can place it against a tile end of the field perimeter and against your robot to ensure its line-up is as accurate as possible. When you get into more advanced things, I would recommend using sensors and possibly coding a PID if you want things to be more consistent. As for your code being “ruined”, it will just take time to tune it, we’ve all been there at one point. Practice/tuning makes perfect.
