![]() |
|
|
At NI, we are creating technical documents, videos and other materials to help you succeed with the new FRC controller, NI CompactRIO. Send us your thoughts and recommendations on what types of content would be most helpful.
realistically, the best thing i think you guys could create is more tutorials like the "hands-on" one already. IMO, the biggest challenge faced by teams for the next FRC season is learning LabVIEW. not that it's overly hard, but i believe that that will be the make-or-break of teams. so, i guess more tutorials on just the basics of LabVIEW relating to the cRIO and FIRST.
Hey tseres,
That is really great feedback. We are definitely working on more tutorials. They are currently being developed. If there are any specific topics within LabVIEW that you are interested in, please let us know. The tutorials are coming shortly.
Keep the feedback coming. It is greatly appreciated.
Thanks
Sarah S
This past year, I decided to write a dashboard VI for our robot. This experience was my first when it came to LabView.
I would like to think that I used preferred methods in my program, but I have a sneaking suspicion that this is and will be a common problem area
I think one of the best resources would tutorials on programming basic tasks in LabView using Best Known Methods (BKMs) as well as tutorials on how best to avoid Worst Known Methods (WKMs). If we were to have a wiki area dedicated to existing KMs and adding new ones from the userbase and NI, I'm sure that teams would be that much more capable in the coming years.
Thanks,
--Adam
It would be helpful if you can show us how to use the NI Compact Rio. This extremely broad, so let me give some examples.
Tutorials on how to program the cRio, specifically how to use the cRio "addon/toolkit/driver" that comes with the cRio for LabVIEW
How we will be connecting to the cRio and communicating with it. I understand we will be using a wireless connection, but how will we program that connection and how can we use it?
How to us the digital sidecar (I think that's what it's called) to convert I/O into PWM I/O.
Maybe some recommended ways on how to switch from autonomous mode to teleoperated mode?
And don't forget all the C users out there.
Thanks alot, I think this community that you've set up is really nice.
As a mentor, the biggest assistance would be a fall series of tutorials in bite sized pieces. By the time the controller and bot came out, the teams would have the concept understood and will have asked all of the obvious questions.
The other contribution would be possibly releasing beta default programming ahead of the robot release to allow experimentation in fundamental LabVIEW programming.
The program looks very robust.
Thank You
Myrle McLernon
Team 2339
I thought of some more examples to my earlier post.
Could you tell us the difference between the cRio we will get in the kit and the one you currently sell?
Can you discribe the Oporator Interface that we get in the kit? (if you can release this information, of course, although they did have OIs set up at the displays at Atlanta, Georgia)
Discribe how we can attach the cRio to our robot. Are there screw holes?
Can you discribe the default code that we will get from FIRST for LabVIEW and C? This year we got default code from FIRST for C and we usually had to just plug our PWMs into the right spot and we would have a moving robot. How will the referies interfere with our robot if they want to disable us? (again, if you can release this information)
I realize now that you were asking what type of resources we wanted, not what was in them. I hope this helps out anyway, though.
I agree with Myrlem. It would be nice to be able to know the basic, obviouse things, and the concept of the cRio. Looking for information about LabVIEW and the cRio is just like what teams used before the kickoff. Any new members would look online and at past manuals and get to know enough about the programming and such to have the general idea once the real work started.
Hey LabVIEWEnthusiast,
I wanted to address the following question that you had:
"Could you tell us the difference between the cRio we will get in the kit and the one you currently sell?"
The NI CompactRIO that you will get in your kit is very similar to the one that we currently sell. However, it will have a few modification specifically for FIRST. The cRIO that you will recieve will have a static FPGA which is significantly different then the currently sold cRIOs. The modules that you will recieve are the exact same as the ones that are currently sold.
You can find more information by referencing the following Data Sheet: NI CompactRIO Specifications.
"Can you discribe the Oporator Interface that we get in the kit?"
The specific operator interface would be determined by FIRST, so I would recommend that you contact them to find out the specifics.
"Discribe how we can attach the cRio to our robot. Are there screw holes?"
Yes, there are mounting holes already built into the cRIO chassis for attaching it to your robot.
"Can you discribe the default code that we will get from FIRST for LabVIEW and C?"
You will receive default code that will enable you to do different actions. The specific tasks that you will be able to do are being finalized and will be released with the software found in the Kit of Parts.
I hope that is able to answer the question, please let me know if you had any other questions or would like for me to clarify anything else.
Thanks
Sarah S.
Applications Engineering
National Instruments
Can you discribe the default code that we will get from FIRST for LabVIEW and C? This year we got default code from FIRST for C and we usually had to just plug our PWMs into the right spot and we would have a moving robot. How will the referies interfere with our robot if they want to disable us? (again, if you can release this information)
The default code for next year will consist of a number of resources:
Libraries that will help you access the parts on your robot like sensors and motors, driver station values, and field settings. C/C++ library will be designed so you simply add your code to Autonomous() or OperatorControl() functions/methods that will be called at the right times during the competition. You'll also be able to control the state of the robot from switches on the driver station. All the C and LabVIEW source code will be open source so all teams will be able to review, modify, and hopefully suggest improvements back to the authors.
Many sample programs that will demonstrate the use of all the components of the libraries.
And other code still being developed
You can use the libraries as is by calling the functions/classes from your programs or you are free to grab the source code and modify the libraries to meet your requirements. Although the hope is the code is sufficiently extensible that you can customize it without modifying the source code.
Brad
Questions for 1.
Does that default code apply only to C/C++ or to Labview also? Will Labview be coming out with default code or will it be like EasyC where it's so easy to use that you can just start programing from scratch looking at the examples?
Also, when you say teams will be able to control the state of their robot from the driver station, I assume that is for autonomous testing during the build season. Are we able to set the channel that the robot is operating from the driver station as well to operate two robots at once?
If teams are just starting to learn Labview, how does the FRC edition differ (other than the examples that will be included)?
Hi cabbagekid2,
The LabVIEW software will have multiple examples. The goal is for you to have access to simple examples that demonstrate the available sensor and output features. You could then potentially copy and paste all the simple examples into one VI and integrate them all into one program. Of course, you can also start from scratch and build your program using the examples as templates.
I've never used EasyC, so I can't compare what will be available with relation to this software.
From what I understand, each driver station can only control one robot.
The LabVIEW FRC edition was built from LabVIEW 8.5.1. Of course, an overhaul was done. You will have custom palettes that allow you to access your FRC sensors and outputs. Most of the other palettes (math functions, loop structures, etc.) will also be included.
I hope this helps,
Kevin S.
Applications Engineer
National Instruments
Hey All,
Thank you again for your feedback. We will be taking these into consideration and creating the appropriate tutorials. It will take a little bit of time, but we are working on it. We will be releasing a few LabVIEW documents shortly, so be sure to looking for those.
Keep any additional feedback coming in.
Sarah S
Since there is a lot of training resources on the NI web site already - I would like to a list of which ones you would recommend we go though. Developing new ones is great - but leveraging what you have makes sense to me.
Rob Steele
Rob,
There are a lot of training resources on ni.com. So many that giving you a huge laundry list of links would likely be unhelpful. My best recommendation, if you are interested at looking at the training resources we already have, is to search a particular topic on ni.com. If there is nothing on that topic or if the topic is overly advanced or confusing we want to hear about it!
Great Idea.
If there are teams that have set up a training course using the NI resources it would be great to post it here so others may follow it.
In My NOT SO HUMBLE OPINION...NI and FIRST should release the basic code during the fall since this is a big change from the past. That way teams can start working and understanding the basic code for controlling the robots.
David
Mentor Team 399
LA Regional Chairman Award Winners 2007, 2008
David,
In addition to the online training already avaliable for LabVIEW, National Instruments is developing training that is specific to the CompactRIO and VI libraries that will be shipped with the kit of parts. This training should be avaliable before the kits ship. The code should be faily intuitive and easy to implement especially if you have already become familiar with the LabVIEW IDE and LabVIEW coding concepts.
The goal of the switch from C/C++ to LabVIEW is to encourage teams to focus on higher level engineering problems and speed up the code development process.
-Mark
<span class="jive-thread-reply-body-container">Mark:
The key to make this change over a success is your statement of "This training should be available before the kits ship." It is already July and the summer is slipping away. Our schools start August 11th and we would like to have a good 4 months of training prior to kick-off. We should not wait till the whole training is put together but just release it in moduals that we can get going... The bad part is lack of access to the CRio hardware to "play" with...
I think that it would great if the teams got softwear with a pre- created eathernet conection to the robot for easy aplication creation.
The most helpful, free, self contained set of slides and exercises for learning LabVIEW is the "Teach LabVIEW in 6 Hours" material from http://www.ni.com/academic/resources_how_teach_lv.htm. It covers core LabVIEW topics that are extensible to LabVIEW Real-Time and FPGA that are used in CompactRIO.
When I'm trying something new, I love to see specifics. That is; someone going through all the steps to do either exactly what I'm trying to do, or something close enough that I can pick up what I need.
The videos are great!
Live desktop captures with audio are really great too. (We use CamStudio)
A nice thing to see is how to get started with a new piece of hardware literally right out of the box. Unpack it. Connect it. Get data.
This stuff is all easy once you've done it. But for first time users to new hardware it could save a lot of time.
pallen wrote:A nice thing to see is how to get started with a new piece of hardware literally right out of the box. Unpack it. Connect it. Get data.
This stuff is all easy once you've done it. But for first time users to new hardware it could save a lot of time.
There will be a video walk-through of how to do this included our first "phased" release of training material next week!
My biggest concern is that my students are not inclined to use Labview and want to use C/C++ (well they want to use C++ and I'd rather they used C). How do we prep the kids to write code in a vacuum? Access to a framework, and a simulator would be fantastic. I'm concerned that we are going to find ourselves in January with having to use default code, and the learning curve is going to be awful. I'd really like to have some way to prep the kids before January.
Any suggestions would be helpful.
