For those of you who are interested, I’ve uploaded my code from the 2010-2011 VRC Competition season.
Written in EasyC V4 (Version 4.0.2.0), the code is comprised of over 2000 lines and includes all of the following:
2011 World Champion Programming Skills Challenge Routine (see the user function “Programming_Skills_Challenge”). A 98 point Programming Skills Run can be seen here: http://www.youtube.com/watch?v=kkHCCKLZsvY
five 20 seconds autonomous routines for each position (see the User function “Auton_Routines”).
-An extensive array of scripts that allow for precise and efficient control of the manipulator during the driver control period (see the user functions “Driver_Control” and Script_Functions" and “Motor_Drive”.
This code represents a tremendous amount of work. The final version that you see here took several months to write and perfect. I used various PID and proportionals loops to control the robot not only in autonomous mode but also during driver control period as part of the manipulator’s scripted control.
If you have any questions about the code feel free to ask.
In closing… I would like to say great job to all the teams who competed in Orlando and I wish you good luck next year! The 2010-2011 season was my last year to compete in the VRC (the team number 1103 is now retired).
Josh – on behalf of the VRC community thank you for sharing this. You have been a great competitor and we will miss your participation. Best of luck with your future endeavors.
My entire team and I have tremendous respect for you, not only as a competitor in Vex, but as a person too. For one, you’ve inspired nearly everyone with your outstanding performance these past few years in terms of building and programming. You represent the engineer, problem solver and inventor that we all strive to be.
During the World Championships, I remember coming up to your pit with another member of my team to ask you about some problems we’ve been having with pneumatics. Instead of simply brushing us off, you decided to spend time and effort to fix our problems. Despite all your fame in the Vex community, you still retained the compassion to help a team you didn’t know. That’s what truly makes Vex such a great program-- knowing that there are people like you in this great community.
We have lots to learn, so thanks so much for helping us and posting your code.
Though you won’t need it, good luck on your future endeavors!
This is possibly the best code ever written for a VEX robot. What a way to leave a lasting legacy - I’m sure that at least Team 254 will be teaching this code to new programmers.
One question I have is that since you are using easyC V4, is there a way for you to post the a text-version of the code? I do not own a copy of easyC, but would really love to look over your code.
Unfortunately, as the code is “rather large” it may be difficult to post a text-only version. You can get a trial version of EasyC V4 here: http://www.intelitekdownloads.com/easyCV4/
Thank you very much for posting this resource, I know it will be an incredible help to new and experienced teams alike. You have been an excellent competitor these past couple years and i know you will be missed. Thanks again for adding so much to the VEX community and best of luck in the future.
Like other commenters, I want to personally thank you for all you have contributed to the Vex community and the inspiration you have given me. You have shown us all the incredible accomlishments that a single individual is capable of. I have been following your robot this season and what you have shown us all is truely incredible. I am trying to get my FRC team to also do VRC next year thanks to you. Best of luck in college!
I (and others) have requested that EasyC provide a text export function, but all we get is “We take that idea under consideration”.
Aha, On project explorer tab of EasyC, there are options for open C file, open h file, convert to C,
The open C file option opens a window that is cut/paste-able to a text file.
I’ll cut all the sections and paste them into a text file, and post it here for Jordan.
Naturally, it won’t be useable in RobotC as is, but at least it can be recut-paste inserted into RobotC by chunks, if desired.
Much better than the .tif file from MSdocument image writer output.
Thanks Josh, I look forward to looking at your code and sharing it with our team. Team 1163 from Parker. It was a pleasure meeting you at Nationals and worlds! Best wishes to you and your family and make your future be bright!
Kevin Barrett
Here is a version of the code as a .c file. It is broken down into the original format but make sure you refer to the structure in the original code so you don’t get too lost in all the lines of text! Hope this is useful for all 1103 Code Text.zip (12.4 KB)
Wow… I’ve just been skimming over the code, and you’ve already inspired me for next year’s code! Joshua, you have really inspired us. I’m sorry to hear you have finished competing, but I wish you well in whatever you will do in the future.
The CORTEX doesn’t have a “tiny memory”. The PIC had a somewhat small amount space for code and whatnot on it, and we usually had to keep our code within 40KB. This year our code takes up over twice that amount of space with over 2000 lines of code, and we can have that much code because of the CORTEX. With the CORTEX I believe you get 32 times the PIC’s amount of space, so you should virtually never max that out.
The PIC had a somewhat small amount space for code and whatnot on it, and we usually had to keep our code within 40KB. This year our code takes up over twice that amount of space with over 2000 lines of code, and we can have that much code because of the CORTEX. With the CORTEX I believe you get 32 times the PIC’s amount of space, so you should virtually never max that out.