- Noise is BAD.
- Keep your SPI cable as short as possible, and mount it on the very TOP of your robot, period.
- Plan out your proto-boards, and start soldering them early.
- Drive Trains are key. Come up with a robust design and get your alignment down. Figure out how you’ll be connecting things to the motor early - couplings, make your own, or order them early. If using belt drive, spend the money on some good stuff, it’ll save you time.
- Enable Interrupts
- Watch out for missing ‘break’s in your switch cases.
- Create debug modules in code that allow you to test each circuit, its inputs, and outputs just by pressing buttons on the keyboard (getchar()).
- Make the sensing circuits early, iterate, iterate, iterate.
- If you’re using an LM324 to sense a signal, stop where you are, and upgrade it to a better chip.
- Yes, there does exist a low drop-out power regulator.
- Talk to other groups to find out how they solved the same problems you’re encountering.
- Kill switches are trickier than you think. Check with a TA to make sure you’ve designed them correctly.
- In the early debug stages, if something smells, cut the power immediately.
- Put it all together early to be able to test your state machine.
- Nap in shifts.
- Keep utensils, bowls, and plates in lab.
- Ultrasonic sensors are easy to use and totally worth the $30.
- 219 Designs has an incredible laser cutter. Take advantage of this.