Some basic questions from a newbie Robotics team

RobotMesh or PROS taking a little longer to support a sensor (usually within a month) doesn’t change the difficulty of learning the software. I don’t know why you chose a quote saying the difficulty of PROS or VEXcode should be same and then talk about integration delay after.

But on the topic of integration delay, it’s generally smart to wait for other teams to test new sensors before buying them. The recent sensors have been pretty good, but I couldn’t rationalize spending $50 on the IMU when it first came out without first hearing good things from team and seeing side by side comparisons with the old gyro.

If you’re a team that buys things when they come out and you use PROS or RobotMesh, yes you’ll have to wait before you get to play with it.


Okay, I’ll stop being a devil’s advocate and give my point.
My argument is not to make a claim that one is better than the other. My argument is the component of “It just works.” Why would 95% of computer owners use Windows when Linux is leagues faster and more efficient? The simple answer for Windows being more of a dominant operating system for the masses is “It just works.” All you need to do is hop onto the VEX downloads page, click install for the software you desire, then you’re good to go. Just a couple of clicks for installation, and even the embedded API right in the IDE. Nearly everything you need to at least get your robot moving, and you do not need to hop onto VEX forum to see if a sensor you bought on the VEX website finally received integration because in VEXcode, the maker for the sensors is next to the the same maker for VEXcode. Everything is right there, couple of clicks, and a snap of a finger with no delay to use all of the sensors and components in VEXcode, and this applies to other aspects of the IDE as well. You could always switch to PROS later once you realize VEXCode has its limits.


I feel like VEXcode is more successful than PROS by the majority of individuals in VEX (although I admit more competitive individuals tend to use PROS more).

Looking at PROS API:

As you can see, you are presented with loads of places and information. That’s usual and nice, but I feel like much of what it offers seem unnecessary, or “fluffy”

What does all of these things mean? There’s no good detailed description, and no preview of a function. I feel like this is inconvenient from a newcomer’s standpoint.

I feel like most people will not understand this structure nor devote the time to understand it unless they have the motivation to do so.

From a newcomer’s perspective, this is incredible confusing. I feel like if PROS want to make itself presentable to newcomers, they should show the function without the std:: nonsense to make it easier for newcomers to properly understand and write the function, or possibly include a side-by-side comparison of the prototype and function? I feel like how it is now, it is far more difficult to understand than Python’s API and almost any community-made API written in Python on Github. In a day of age where coding is simpler for the majority of the population, I do not feel like the presented information matches the status quo of how things are going in society when coding.

Most of the stuff I need should be presented directly in front of me, with no unnecessary fluff. Then the more advanced code should be categorized as such. Look at Google’s settings. Most of the stuff you need is there, but if not then you click “Advanced” tab at the bottom.

The objective of VEXCode V5 is to teach you what everything means, then when you transition to VEXCode Pro V5 you would no longer need a crutch of extreme “push-to-your-face” information.

I would like to provide how to access documentation for VEXCode functions. I want to see the functions of the motor. Looking at it I see… No motor functions?

A newcomer would likely figure out that it adds functions based upon sensor setup. Adding a motor to the sensor setup, looking at the area again…

You can see there is all the functions 95% of most individuals in VEX need, categorized neatly. But what does each function mean or how would a newcomer use it? They would simply click the “?” next to motor.spin for voltage and a “Help” section pops up on the righthand side.

As you can see, it is straight to the point with VEX’s Embeded API. And it’s directly in the software.

Now, it is about as easy in VEXCode pro…
When coding, you can view the functions of the motor as such:
Screenshot (4)
I want to learn about current, so let’s press “Enter.”
Then, a newcomer would right click the function in the code and I click “Command Help”
Screenshot (5)
It then asks me which type:
Screenshot 2021-09-06 215156
They would want to see what MOTOR.current() does, so they click that.
Straight to the point, in a manner that I feel like 95% of individuals in VEX should understand.

From what I can see, I feel like it is not correct to assume that PROS is just as easy as VEXcode. I feel like VEXcode offers an easier way of making information understandable and presentable in a manner that is clean and straight-to-the-point without fluff.

1 Like

Connor, the aggression, disrespect, and lack of professionalism displayed in your post is uncalled for and actively inhibits the process of productive civil discussion. I would respond to your points respectfully, but the tone of your post is so incendiary that I doubt any further productive discussion would result. If you truly become this upset because a member of the forum respectfully disagrees with you, then I suggest you take a break away from the computer before coming back and taking a second look at the situation to determine if there is a good reason to be so upset. There is no need to use such condescending language in the course of a civil discussion on this forum. Such language is unproductive and does not foster a welcoming environment, something that is especially important when it comes to welcoming new teams into the competition. When you have to begin a post with “Honestly, this may sting a bit”, that should trigger a self reflection on if what you are about to post is truly worded in the most productive manner.


You are correct that I was disrespectful, and I am sorry.
I am sorry for an aggressive tone @Unionjackjz , you did nothing wrong. I will edit the post to be civil.
Much of what I said came from an aspect of feeling, which was wrong.


If you’re experiencing these issues with VEXcode, I would ask you to please use the feedback tool built into VEXcode to report “crashing” or other issues. We can’t fix issues that we’re not aware of, and these issues you mention have not been previously reported.


Just wondering with all the talk about pros vs vexcode

What program do you use?
  • PROS
  • Vexcode text
  • Vexcode blocks
  • Other

0 voters

I reccomend not buying a kit I would look at reveals and buy individual parts

Polling other programming religious wars :wink:

  • 2 Space indentation
  • 4 Space indentation
  • Randomly indent
  • No white-space at all, no newlines - code was hard to write, so it should be hard to read!

0 voters

1 Like

Didn’t even include tabs?

I am a strong proponent of tabs over spaces, with tabs anyone can configure their text editor to display a tab to be as large or small as they would like.


The latest version of the Competition Kit, IMHO, is a good place for a new team to start. It would be difficult for a new team to pick out the necessary individual parts from looking at a reveal,


Griffin, you may want to reconsider that unfortunate view…


I have to agree with @536Mentor, the V5 competition kits were well designed (unlike the old Cortex Clawbot kits). The competition starter kit is a good choice for a novice team, as it includes the parts to build the V5 trainer, while the competition super kit is a good choice for established teams (you cannot build a the trainer with the comp super kit). Additionally, the kits provide up to 25% savings over individual part prices, and since VEX never has a “sale” it’s the only way you’ll ever get a discount from VEX. For anyone interested in making cost comparisons, here is the data: V5 kit contents-2-3-21.xlsx - Google Sheets

1 Like

Correlation does not imply causation. Tabs are superior.



20 whole characters

1 Like


1 Like

You can’t build the clawbot with the competition super kit, but if you buy the claw kit separately (link) and do a bit of cutting, you can end up with something very similar.

But for competition use, I think you’re probably better off with the hero bot as a first build anyway – and you can build that from the super kit, although some cutting is required:

Or at least, you can this year (and IIRC you could last year too) – no guarantee that next year’s hero bot will be buildable with the super kit, but looking at the selection of parts in both kits I would say it’s likely.

Given that all the parts in the super kit are useful, and that it offers the most savings compared to buying all the parts individually, the super kit is definitely what I’d go for if it’s in the budget. If not, the starter kit is a great option.


Thanks for all your great reply. So in summary here is what I learned:

1). Programming - VEX code (C++) or PROS both great options - with great support and easiness to learn. VEX code has python support also - although numpy and some other support needing - so give it another year? Don’t want to start another language debate, but we will probably start evaluating C++ options.

  1. Getting the kit - VEX V5 starter kit of Competition super kit - and building a clawbot or hero bot. We just got a Competition super kit by the way. Hope to start to play on it, and not cut too much as we want to work towards our eventual double intake model.

Looks like Vex education channel is great for initial. Clawbot manual is there. Does people recommend a few lectures to get familiarized with different components, or perhaps we just dive and start building the claw bot?

Thanks, we learned a whole lot


I think that the learning will be the most genuine if you just dive into it and ask questions along the way instead of listening to a monologue about the fundamentals of VEX Robotics. Experiment with different things, find what works, what doesn’t, just make sure they aren’t bending any metal (except for plate metal, I suppose that’s acceptable; let the debate ensue), overheating motors, or causing damage otherwise out there. There’s plenty of resources on YouTube if you are looking into cool ideas to try building.

1 Like

Here are some good resources to get you started, too.