Thread: (Programming) Lessons learned from week 1?
View Single Post
  #6   Spotlight this post!  
Unread 06-03-2011, 20:32
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: (Programming) Lessons learned from week 1?
I had a great time in NJ and met quite a few people face-to-face that I otherwise wouldn't be able. It is good to mix things up.

The things I saw in week one which are easy to learn from... not necessarily code related...

1. Connect the dlink properly. Connect it to the boosted 12V on the end of the PD marked for the radio, not to a typical red/black fused 12V circuit. Also, I'd suggest using the voltage regulator. If you do not do this, your robot will lose communications whenever it starts pushing another robot and power droops.

2. Run your code through a practice match on the DS. A number of teams using Java or C++ had code which didn't leave auto. It worked fine if you only test tele. It may even work if you only test auto. The field sequence is what you care about and the DS practice match is a good approximation to that. We also saw teams who's auto managed to cause errors in tele.

3. If you are using CAN, pay attention to error handling and to cable termination. Errors that aren't handled well and aren't reported to the field may take out much of the robot and cause lots of debugging confusion.

4. Know what the latest update versions are and check to see if they have been applied. DS should be 1-05-11 or 2-27-11. Robot should be v28. You may need development tool updates as well, and I'm not listing all of those.

5. Don't disconnect the cRIO from the dlink. Direct cable the DS and development computers into the dlink. If you disconnect the cRIO, you will forget to reconnect. You know you will, so just leave it connected at all times.

6. Pay attention to the switch on the back of the dlink. It should stay in bridge mode for the competition. If it gets knocked to auto or AP, your robot will disconnect or not connect at all. Also pay attention to the barrel power connector to the dlink. If wiggling it causes the dlink to reboot, this will also happen on the field.

7. If you are using the M1011 camera with C++, be sure to get the WPILib patch.

8. If you use LV, and your CPU usage is high, move the compressor code to Begin. Turning it on each teleop packet adds more overhead than you think. The code was written to be started in Begin.

Greg McKaskle
Reply With Quote