How do you use the motor encodes for driving straight? We looked and didn’t see any text that addresses the individual motors in a drivetrain after you set up the drivetrain (in the vex code text). You would find the velocity of the motors and make a loop that continually decreases one to the velocity of the other so that they’re always equal right?
To be honest, we never really experienced much issues with this. When programming things like skills, its always important to put consistency over everything, including score. We always say that a reliable 50 is more important than a “sometimes 60”. In cases where the robot may require failsafes, we run slower, and make up for it in areas we can accurately run fast.
I realize that VexCode Blocks was made to simplify things. Our kids are familiar with it but have not made the leap to text based or other programs like RobotC. One area that I think is not addressed very well in online literature and tutorials (read: youtube) is using VexCode Blocks at the highest level it is capable of.
If your kids can give instructions on how to use VexCode Blocks to it’s absolute limit, I believe you would find an appreciative audience.
Our kids are preparing some videos to help new teams to get started, it’s work in progress. Stay tuned, we will post them as soon as they are ready.
That sounds amazing! This would benefit a lot of teams. Could they please include their code/an explanation of it? We’ve been having similar problems as Robotics17481A. Also, we use the vexcode text. Is robotC necessary?
I think a great enhancement to Vexcode GUI would be to have a UI field in the setup to define the power /velocity per motor when defining the drivetrain. This would be a great compromise (esp. for elementary kids), as doing so lets you manually try and adjust power levels to straighten driving out. Who do we tag for enhancements?
So that said, could you build all your logic in codeblocks gui and then convert the project to the text project and just paste some of the code you can create in robotC for setting drivetrain velocity, syncmotors, ect? Seeing if anyone has gotten this to work? Wasn’t sure on the motor naming as the RobotC samples defines the drivetrain motors as B and C, not sure how that translates over with what Vexcode spits out.
How do you even do PID? I keep looking around for information, and I want to make my autonomous more accurate.
Check out this document by George Gillard:
Thanks, that helps a lot.
Can you do PID in VexCode IQ Text?
Yes.
How? (20 characters)
Did you read the document? It should be easy to set up once you understand the fundamental principles
Yeah, but I’m really new to robotics; it’s only my first year, so I can’t understand things like that yet.
If you still want to use PID, then you should also watch this PID tutorial by @ Connor (it’s for V5, but the concepts should easily transfer over to VEXIQ)
If it’s still too hard of a concept to understand & implement (which I totally understand btw), then there are other things that your team can do to have a more accurate autonomous program (moving at slower speeds, aligning the robot against the field perimeter [only works if your robot is only using Omni wheels], etc.)
Thanks, I’ll try that.
Could you please explain how to create these motor encoders? We’re using vexcode should we use RobotC? Also, for PID did you use a distant sensor or was a gyro enough? Thanks
are you sure that part is allowed?
There are several lengths of rope listed in the legal parts appendix (page 27).
In general, non-electronic parts from HEXBUG VEX kits are legal for use in VIQC.
Curiously, the 36x pitch rope (228-3943-440) that @sidoti mentioned above is not listed in either the legal or illegal parts appendix - but I can’t imagine it would be ruled illegal given that all the other lengths of rope are OK.
That is because the Legal Parts Appendix only gets updated at regular intervals. Sometimes parts get released after the newest revisions of the parts appendices. Check for it the next time the appendices are updated!
But you are correct. It should not be considered illegal as it is a normal VEX IQ part just like the rest of the rope lengths.