Quote:
|
Originally Posted by Noah
1) Programming will take more time than you expect, especially if you want autonomous to work. Tell the team that the robot needs to be driving and in your (the programmer's) hands with at least three days before shipping.
2) Rookies: Don't program without sleep. Sure, you'll hear the experienced programmers bragging about a 36-hour code marathon, but all that means is that they are good at procrastinating. And working without sleep.
3) Don't forget to initialize a variable you are using as a PWM output to 127.
4) Increment your counters! (One year my robot span around in a circle for about three minutes...)
5) If at all possible, make sure the code works *before* dumping it into your robot
6) When testing your robot, lift it off the ground. Prop it up somehow. This can save lives! (well, shins, anyways)
Good Luck!
|
1) The dangers of killing people and dangerous situations etc can be avoided by using/making/building a dongle .Trust me its worth building that.
2) Things in theory are not always right practically. You can calculate how far your robot will go in a certain time, but when you do it practically you might find different reasons. For that reason everyone tells you to reserve a lot of time for programming autonomous.
3) Most of the time if you find a problem, look Though a C guide for syntax, or the Innovation FIRST programming guide, simple mistakes can cause you to go crazy. I agree to Noah, sleep is important, it helps you take it easy and not go bonkers programming.
4) Step by step: Don't write the whole robot code in one shot and expect it to work, do it step by step i.e. part by part, drives first, then arm, then other stuff....
5) Will think up more and post later...