Go to Post I always mean what I say. I just don't always say what I mean. - dlavery [more]
Home
Go Back   Chief Delphi > Technical > Programming > NI LabVIEW
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #8   Spotlight this post!  
Unread 25-05-2009, 10:33
Luke Pike's Avatar
Luke Pike Luke Pike is offline
Programmer
FRC #1501 (THRUST)
Team Role: Mentor
 
Join Date: Jan 2008
Rookie Year: 2008
Location: Huntington
Posts: 114
Luke Pike is a name known to allLuke Pike is a name known to allLuke Pike is a name known to allLuke Pike is a name known to allLuke Pike is a name known to allLuke Pike is a name known to all
Re: The "Right" way to program

When I programmed the robot this year, my process went like this.

First, the team decided what they wanted the robot to do. It was a very specific process, by the time we were done we had a list of all the features our robot would have, roughly sorted by priority. This is what the robot would do and nothing else.

While the design and mechanical teams were doing their thing, I would give input on the feasibility of programming a particular feature of the robot, whether I could use these sensors to control that thing to do this, etc. Of course, sometimes they have to do it a certain way, and I'll just have to work with it. Once the teams had finalized what the final devices were going to be for the feature(of course this might change and usually does), I would begin programming it.

The first thing I do when programming a feature is to think really hard about how I would do it. I'm talking like pacing around the shop deep in thought hard. The advantage of this is that I can catch problems before I even start coding. I usually go through multiple ways of doing it, and finding all the disadvantages and potential bugs. Once I have a good idea of how I'm going to do it, then I start to code. I test individual pieces as they are completed, like sensor reading, processing, and the like. LabVIEW is really great for this part, because I can run it on the cRIO and still get the front panel values.

The first time through it almost always fails, but that's to be expected. After running through it over and over again, I find the bugs and squash them. Sometimes it's a really stupid human error on my part, sometimes it's something that a sensor or part can't do and you have to find a different way. In the end, it gets the job done, sometimes in a completely different way then when I started.

This is the way I personally programmed this year. You can do it mostly any way you want, as long as it works for you and your team.
__________________
Twitter Profile
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
What's the difference between "The Great Attractor" and "Dark Flow" Woody1458 NASA Discussion 0 04-05-2009 22:17
Championship Event - Where the "Random" Match Sorting Really "Shines" Travis Hoffman Championship Event 57 19-04-2007 08:06
Program error - "can not fit the section" miketwalker Programming 9 20-02-2005 01:21
The exact name of the program "gift" we are to download? Flynn Programming 2 10-01-2005 21:47
"Thunderbirds" Vs. "Team America" Which one will rule the box office? Elgin Clock Chit-Chat 3 07-09-2004 19:53


All times are GMT -5. The time now is 21:55.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi