First of all, that code was not anything remotely good or tested. I am also a beginner when it comes to C++. I recommend learning C++ or Python basics first. Then, you could use VexCode Pro Command Reference and your own C++/Python Knowledge to program the robot. By the way, everything outside the int main( ) was automatically created by VexCode pro during configurations. You should ask others for more help, because as I said, I am a beginner to C++. I would recommend the W3 schools site for now.
I think the Pneumatic launcher is a great idea, it could open up new possibilities for uses of pneumatics. I was personally thinking that I would use a conveyor belt system but not a launcher, because a launcher would be pretty unreliable (Though still a frickin cool idea) I think the most secure option would be an arm that extends out (connected to the conveyor belt) and just plops the discs in. This would be a very good strategy if you built a storage system and collected a bunch of discs and just went ham on the goal.
Did you read the manual? There is a limit of 3 disks per robot at any time, and the height limit for the robot is about an inch above the maximum height your robot will ever be allowed to reach.
Oops sorry, I haven’t had time to read the manual thoroughly.
Made of foam but lightly weight stuff like the field tiles. It’s 20 grams so 1/3 of the weight of the regular discs but at least we got the approximate shape to work with
Would the vision sensor be accurate and efficient enough for this? My team was thinking about this idea but didn’t know how exactly to execute it. Could the vision sensor end up overshooting or would it work for this concept?
The Vision Sensor, if I am correct, will only be able to be used for directional purposes. When it comes to power, you would have to use some other methods. The only way that we could reliably use the vision sensor to show distance is if we used the VISION.objects.height; and width function and compare this value to the actual width. Then, we could adjust RPM according to the scale. As for the efficiency, I believe it will be enough for this task, but I may not understand your question correctly.
Yeah, I was thinking about using it for directional purposes. Sorry, that might have been a bit confusing. I meant overshooting the turn. Would the vision sensor detect the goal while the robot is turning fast and align correctly or could the robot overshoot? I’m not exactly sure how quick and accurate the vision sensor is with putting out values I’ve never used it before.
So you mean overturning?
Yeah sorry if that was confusing
I recommend single flywheel, I’d these act anything like a Frisbee you want spin on them so they fly somewhat accurately
I am pretty sure that the vision sensors are accurate enough to pull this off. I did not trust them either until this:
Yeah vision sensors or the optical sensor could work for this probably. Thanks!
seems fine to me
For Python specifically, I recommend Automate the Boring Stuff with Python (link may work). Python is really good for teaching the basics of coding, though, so if you have free time (summer break for instance), I highly recommend you go through the book even if you plan to do C++. W3Schools is a good reference site, as @Paradox-E mentioned.
The vision sensor doesn’t turn; it’s up to you to make code that will make the robot turn quickly but not overshoot. (Hint hint: learn PID.) It seems kind of weird to say the vision sensor is “turning quickly” or “overshooting the turn,” since the vision sensor is not driving.
Oh that’s true thanks. Our programmer already used PID for auton last year and it worked really well so that’s probably what we’ll be using again this year.
So like only 1 side?
precisely that, you only want one wheel, so the design would have to change a little but it’s still very plausible
The disks are made out of foam so does anyone else think that they will get destroyed fairly quickly?