View Single Post
  #13   Spotlight this post!  
Unread 25-04-2008, 22:12
Danny Diaz's Avatar
Danny Diaz Danny Diaz is offline
Smooth Operator
AKA: FrankenMentor
None #0418
Team Role: Alumni
 
Join Date: Apr 2005
Rookie Year: 2003
Location: Manchester, NH
Posts: 545
Danny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond reputeDanny Diaz has a reputation beyond repute
Send a message via AIM to Danny Diaz
Re: Programming with the 2009 controller

Quote:
Originally Posted by Jon236 View Post
That's true....but what I find inspires these kids is getting them to the point of competency with the programming. I expect them to write the VI's to perform autonomous, control the drives and other actuators and implement feedback control, as well as being able to debug.
All of which I firmly believe will be the case and then some; no matter what we did, if we didn't do that then we'd be doing a disservice to the competition.

Quote:
Originally Posted by Jon236 View Post
I don't expect them to become LabView experts....but I DO want to leave them with that taste of wanting more. THAT's what I call inspiration.
I think that might be going on my quote board. That's what FIRST should be all about.

Quote:
Originally Posted by Jon236 View Post
BTW, will the FRC Toolkit VI's that I have be of any use?
You mean the FRC Simulation and Modeling Toolkit VIs we provided for the IFI controller? Nope. That toolkit was designed specifically for the IFI controller since we couldn't do the kinds of things we can do with the cRIO. Unfortunately we had to look at the IFI controller like a black box, and use the USB DAQ device to programmatically inject "fake" sensor data to make the controller think its sensors and such were actually giving it live data, and then we used the Dashboard to peek at what was going on behind the scenes to see what the results were. With this mechanism the modeling environment was extremely specific, and you were limited as to what you could do (forget modeling the camera inputs!!).

Teams that use LabVIEW should be able to do all this within a LabVIEW environment on their laptops/computers without the need to do hardware-in-the-loop simulations. That way the electronics team isn't yelled at for stealing sensors and the controller. It would probably take an average team a day to a week to set up an environment to model for their specific robot, depending on how complex it is (and, of course, I've never tried modeling crab or meccanum (sp?) drives, so that might require some additional thought).

-Danny
__________________
Danny Diaz
Former Lead Technical Mentor, FRC 418