View Single Post
  #9   Spotlight this post!  
Unread 25-02-2008, 18:05
114Klutz 114Klutz is offline
Registered User
AKA: Li Pi
FRC #2984 (Viking Robotics)
Team Role: Mentor
 
Join Date: Feb 2006
Rookie Year: 2005
Location: Los Altos
Posts: 152
114Klutz is a jewel in the rough114Klutz is a jewel in the rough114Klutz is a jewel in the rough
Send a message via AIM to 114Klutz
Re: Custom Circuit Design

Debugging - keep in mind, there is no port for a debugger on the FRC controller - and printf is a poor substitute for a debugger. Even if you intend to write code for the RC only, it's a good idea to test such code on the circuit board first, so it can be debugged there, and then utilized on the RC later.

The second thing is to offload processor intensive tasks such as keeping track of the encoder count to another processor. While generally, encoders shouldn't make a significant difference, if you use high pulse per revolution encoders and a very fast wheel, you can easily end up with the red light of death.