BEG for Help about V5 VEX Coding Studio

VEX V5 Technical Support
1

I have already used cortex for a long while.But I don’t know how to write program Vex Coding Studio C++ for V5. Since there are not any sample programs at all (or I can’t find them), I can’t even able to download some easy codes.
For example, I want to use the command "


Motor1.setVelocity();

". And then there is error note saying "


note: candidate function not viable: requires 2 arguments, but 0 were provided void setVelocity( double velocity, tVelocityUnits units );

". I tried all the contents I came up with. If I write "


Motor1.setVelocity(67,RPM);

“, it says”


error: use of undeclared identifier 'RPM' Motor1.setVelocity(67,RPM);} ^ 1 error generated.

".What should I fill the blank with?
Furthermore, Why is the VCS so simple? I can’t find any other Sensors except for controller, Limit Switch, Bumper, Vision Sensor and Motor. Maybe I am using the BETA version?Where I can download the official version?( I downloaded it from REDACTED
At last, I beg for some sample programs for VEX coding Studio!! Thanks for your concern!!

2

Hey there! The v5 coding studio hasn’t been released to the public yet, so I’d recommend contacting a beta tester through discord to get some help. I haven’t looked into the code much since I’m still prototyping with v4, but I’d assume that’s the easiest way to do it. Good luck!

3

Yes, you are using the beta version (hence the use of the word beta in both the URL and page title), which is also the current official version. That is, a stable version of VEX Coding Studio likely doesn’t currently exist.

If you’re interested in good documentation, perhaps take a look at PROS. Unlike VEX Coding Studio, I believe downloading PROS for V5 is properly restricted through a private GitHub repository, but API documentation is already available and is probably far better than any documentation that will materialize for VCS.

4

my understanding is that the V5 Pros is still in beta like VCS…

5

Yeah… everything is still in beta…q

6

RobotMesh Studio is usable and documented as well.

7

You have downloaded a version of VCS that is now several months old with minimal functionality, release versions will be much improved. Documentation will be available with the release of VCS, typical motor commands will look like this.


    // Spin motor forwards at the default speed   
    Motor1.spin( fwd );

    // Stop motor
    Motor1.stop();

    // change velocity used for spin methods
    Motor1.setVelocity( 30, rpm );

    // Spin with speed in the method call
    Motor1.spin( fwd, 20, rpm );
8

Thanks, @jpearman ! Also, @Oppenheimer , you can find a lot of the C++ commands specific to VEX C++ listed on the system architecture page: https://www.vexrobotics.com/v5-architecture.html . For example, with motors it gives us

Motor.setVelocity()
Motor.setTorqueLimit()
Motor.setStopping()
Motor.setRotation()
Motor.setTimeout()
Motor.spin()
Motor.rotateTo()
Motor.rotateFor()
Motor.stop()
Motor.startRotateTo()
Motor.startRotateFor()
Motor.isDone()
Motor.direction()
Motor.rotation()
Motor.velocity()
Motor.current()
Motor.power()
Motor.torque()
Motor.efficiency()
Motor.temperature()

@jpearman 's post shows much better how any of these will look when you write them and what input some of them require. But the architecture page will let you see what you’ll be able to do directly with quite a number of the different devices. The architecture page is missing much of this, but it does let you know other things, like “Position and angle are reported with an accuracy of .02 degrees.”

Meanwhile, it’s almost August. Soon… :slight_smile:

9

Hmm. That’s actually looks like a typo, with 36:1 gear cartridge we have 1800 counts per revolution, so 0.2 deg per count.

10

I know. My understanding is just that PROS is much more usable at this stage, with a relatively final API even if not also relatively final implementation (otherwise why would they release the V5 documentation?). Additionally, if RobotC was anything to go by, I fully expect PROS documentation to be exponentially better than that for VCS, at least at launch.