Log in

View Full Version : Which language should we use to program our FRC Robot? Why?

darkgiant
17-01-2013, 00:24
Hello!

I am currently running a rookie team right now, and am somewhat familiar with LabView (last time I actually used it FRC related was three years ago!) so I don't have a great memory on the fundamentals to using it. As of right now, we are making our 'bot pretty simple, 6 wheel drive with shooter using CIM motors. Because of this, I was wondering, which programming language should we use to have our Robot's drivetrain just move? Should we follow the path of LabView? C++? or Java? I may be asking this question sort of late, but I understand that there are some sort of tutorials on how to make this all happen. My team is hoping to have a robot moving by the end of this weekend (as we mounted all of our parts tonight!). Anyways, which language should we program our robot in, that would be less time consuming, and easier for noobs?


Thanks!
bdbayes
17-01-2013, 00:25
I would personally recommend Java, as you can turn out some simple code to get the robot running really quickly. If you have any questions or need help, feel free to send me a message.
darkgiant
17-01-2013, 00:30
I would personally recommend Java, as you can turn out some simple code to get the robot running really quickly. If you have any questions or need help, feel free to send me a message.

May you possible link me to any resources that I can get started with immediately? I never worked with Java, and would like to have something working for my team by the end of this Friday, and later continue my learning improving my code of course. :)
Mugurussa675
17-01-2013, 00:32
My team has been using c++ for the past couple of years and they decided to try java this year. They absolutely love it and don't ever wanna change. So I'd recommend java. If you have any questions about java feel free to shoot me a message :)
F22Rapture
17-01-2013, 00:33
Getting Started with Java for FRC
http://wpilib.screenstepslive.com/s/3120/m/7885

RobotBuilder (optional)
http://wpilib.screenstepslive.com/s/3120/m/7882

Testing programs
http://wpilib.screenstepslive.com/s/3120/m/8564

SmartDashboard & LiveWindow
http://wpilib.screenstepslive.com/s/3120/m/7932

Command-based programming
http://wpilib.screenstepslive.com/s/3120/m/7952


I would recommend playing around with RobotBuilder a bit and looking at the output code, even if you don't plan on using it. It should help you get an idea for the structure of the program.
bdbayes
17-01-2013, 00:35
Here's a copy of some simple code that I helped another team put together. Download Here (https://dl.dropbox.com/u/32298681/FRC2013-Team4166.zip). This gives you a simple set up that should work with most bots. You can open the project up in Netbeans. A lot of the resources for Java are available here (http://firstforge.wpi.edu/sf/docman/do/listDocuments/projects.wpilib/docman.root.c_and_java_documentation). If you have any questions, feel free to ask.
Greg McKaskle
17-01-2013, 06:20
I would suggest either LabVIEW or Java. They are both safe languages and the tools and tutorials will get you up and going quickly.

To go beyond the basics, you should take advantage of experience and interest of other mentors on the team. Ideally the students get some exposure to each of the languages through their FRC years.

Greg McKaskle
darkgiant
07-02-2013, 01:44
Sorry for reviving an old topic! Back to the point, we were messing around with LabView, and managed to get something that moves our motors and drives everything. Now, I want to take the challange and code all of this in the matter of two-three days. With all the links provided above, would that be enough to have an obvious drive train, use gear motors, limit switches and multiple CIMs as a shooter? if there are more resources available, I am open to it!
Greg McKaskle
08-02-2013, 07:11
It would seem like your choice is to keep improving the code you have, or start over. I'm sure that the links are useful, but I think that you or someone on your team is in the best position to decide what is right for you.

Part of the FIRST experience is exposing you to new concepts and tools, but at the end of the build, you definitely want a robot that operates and competes. You don't have to use all the tools, and which tool you select is not as important as how you use it.

Greg McKaskle
darkgiant
09-02-2013, 16:42
It would seem like your choice is to keep improving the code you have, or start over. I'm sure that the links are useful, but I think that you or someone on your team is in the best position to decide what is right for you.

Part of the FIRST experience is exposing you to new concepts and tools, but at the end of the build, you definitely want a robot that operates and competes. You don't have to use all the tools, and which tool you select is not as important as how you use it.

Greg McKaskle

I completely understand the FIRST experience, I had run a previous team for three years, but never touched programming until this year. This year, I had started a team where no student had any knowledge in any programming, and I had decided to go with LabView (as my previous team used LabView every year) so I had a general idea on what I was doing at the time. Now, I wanted to see if we can, together of course make something in Java (I looked over C++, with the time constraints and such barriers it is sadly impossible as of right now, but can be a side project for the off season!) Anyways, I have followed the given resources and have a simple driving robot. If it comes down to not being able to finish it up before bag n tag, we will stick with LabView. But like I have said, if there are more resources (that are possibly noob-friendly) I am open to it!

Thanks!