Quote:
Originally Posted by Danny Diaz
Lastly, using C instead of LabVIEW can be a valuable crutch. Depending on when the controller gets in your hands and how much time you have to learn how to use it, having an out can make you more comfortable with the whole 6 week deadline thing. I would hope that teams would pick up the LabVIEW software we provided in the KOP, maybe even pick up an NXT robot and the LabVIEW NXT Toolkit, and learn how to use LabVIEW in the off season. However, that's not going to be possible for all teams. Giving a way to experiment with LabVIEW but being able to use some C code if necessary can help facilitate teams moving to using LabVIEW without being cornered into an all LabVIEW or all C/C++ situation.
-Danny
|
Danny,
Firstly thank you for your insights and knowledge with regards to this new control system and Labview.
This is most likely the direction we'll take. Subject to change of course.
Or "How I spent my summer Vacation"!
I'm planning on obtaining a Lego Mindstorm kit(~$250) and the additional rechargeable battery(~$50). I've downloaded the Labview NXT toolkit, and will attempt to learn and teach Labview within our Team.
Once the WindRiver, VxWorks, WPILib environment is ready we'll begin work porting our "C" code to it. This may be a bigger challenge, since we don't use Easy C or WPILib today, so some our "high performance" modular routines may not fit as nicely as we'd like.
At least this way we'll have options and choices, and hopefully enough skills to be ready for the new season.