View Single Post
  #5   Spotlight this post!  
Unread 02-01-2014, 17:54
mrscience21's Avatar
mrscience21 mrscience21 is offline
Joe Sandoval
AKA: Joe S.
FRC #3859 (Wolfpack Robotics)
Team Role: Programmer
 
Join Date: Jan 2012
Rookie Year: 2011
Location: Elk Grove, CA
Posts: 14
mrscience21 is an unknown quantity at this point
Smile Re: 20 Minute LabVIEW presentation

I agree with Paul T, 20 minutes is not a lot of time for a labVIEW tutorial. I have been teaching a set of new programmers and have found that in order to do it well you need a much longer amount of time, allowing questions to be answered along the way. In any case, if you are mainly reaching out to new programmers, please make sure you cover a couple of things (Hopefully without repeating someone in the comments above, sorry if I do.):

1. Type Defs, Clusters, and Arrays: I have found that these specifically confuse new programmers quite often. That's a big problem too, since these data forms are used frequently, especially in WPI Lib Functions. Not to mention they are very useful once mastered and can minimize memory usage.

2. Robot Data Flow: This one is critical. A good understanding of Data flow through out RobotMain.vi, the robot and dashboard, and even the flow between the C-RIO and other components can save tons of headaches later. ( This can be as simple as ensuring they understand begin operates before teleop and etc.)

3.Construction of a basic drive system: From "begin" to "finish", this may be the most important thing you can do.

4. Disable.vi and safety configurations: I frequently see new programmers leave these alone, resulting in a flood of errors that can very easily be avoided.

If you wouldn't mind the suggestion, I would hold off on doing an autonomous program but instead demonstrate the construction of a basic drive program from start to finish. Autonomous may be more interesting to watch but it is Teleop new teams will have to worry about. Plus, construction of a complete drive system is capable of demonstrating how the all the subVI's in the system work together to accomplish a single task - moving that robot. In the short amount of time given, I realize you wouldn't be able to do a full explanation of how the system works, but I've found that giving them a basic over view of how and why it works provides them a foundation from which they can expand their knowledge.

If you have more time, please also consider talking a bit about sensors and how to use them. From personal experience I realize the demonstration alone could eat up all your time but this is yet another topic I see a lot of younger programmers over complicate or mess up entirely. Good Luck!
__________________
Joe Sandoval
Wolfpack Robotics FIRST Team 3859
Department of Programming and Electrical Engineering


Reply With Quote