|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||||
|
||||||
|
You received your new control system ... Now What?
Over the next 2-3 weeks, close to 500 teams are going to be receiving their new control systems. I know everyone is excited, but I wanted to share some things that will make everyone's life a little easier.
As you may know, I am on one of the 18 beta teams. Over the past two months, we have been reviewing documentation, writing code, testing the hardware and software, and giving demos. We started with version 0.1 of documents, and have helped them go through 3 or 4 or 5 revisions. The software we started with has now been updated 6 times. However, the documentation and software is still not perfect. We've looked at everything 15 times, so now we don't see the problems. That's your job, to find the things everyone's been overlooking. Now the beta team's jobs are to help the 500 teams who now have the control systems. We're the triage unit to help teams with the easy things, and make sure the real problems get addressed. From the control system manual: Quote:
I think everyone's first idea will be to either install the programming software (LabVIEW, Windriver Workbench, or both) or to install the cRIO into a robot or test platform. While not the worst thing you could do, you'd be much better off following the guide that FIRST put together in section 1 of the control system manual. You'll notice that of 10 steps, installing the software is step 4 and installing the cRIO on a robot is step 8. The real place to start is at http://usfirst.org/frccontrolsystem That is where FIRST has posted the control system manual, along with links to other documentation from NI and WPI. Read section 1 of the manual all the way through. It will point you to where you need to get anything else you need. It has has the 10 step process for getting everything set up, and eventually into a robot. It leads you along in a logical fashion. No matter what you do, don't miss step 2, inventorying the kit within 3 days. You'll proceed along, first hooking everything up in a benchtop test, then verifying very basic functionality. You'll then progress to loading new "images", setting up the wireless, and finally writing your own code. To quote the manual once again. Quote:
I know there will be a lot of questions. That can be a good thing, and that can be a bad thing. Many times, people get excited and ask poor questions. Take a little bit of extra time to reread the manual, and look around for the solution. More times then not, someone has already had your problem. Now that I got that out of the way, to quote the manual again: Quote:
You'll notice that I quoted quite a bit from the manual. That's because many people at FIRST, NI, BAE, and WPI put a lot of time into the manuals, along with all the beta teams. It's not perfect, but you'll get much farther if you read it. I'm finishing up a few cool (in my opinion) examples, so keep checking the beta forums for those too. Here's to a great control system and a great season! Last edited by Joe Ross : 19-11-2008 at 22:49. Reason: typo/grammar |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 2009 FRC Control System Forums Open now | BornaE | FRC Control System | 7 | 01-10-2008 19:02 |
| What are you all using to hold down your control systems? | JackknifeJustin | General Forum | 10 | 02-02-2008 12:24 |
| How old were you when you got your first real job? | Ashley Christine | Chit-Chat | 31 | 24-08-2005 13:58 |
| What do you wish you knew about the new control system? | Joe Ross | Control System | 2 | 09-01-2004 21:47 |