View Single Post
  #10   Spotlight this post!  
Unread 06-03-2011, 22:02
theprgramerdude theprgramerdude is offline
WPI Freshman
AKA: Alex
FRC #2503 (Warrior Robotics)
Team Role: Mentor
 
Join Date: Feb 2010
Rookie Year: 2008
Location: Brainerd, Minnesota
Posts: 347
theprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud of
Re: Question: how many encoders can be used on the robot?

Quote:
Originally Posted by apalrd View Post
The rate bug is in the FPGA image, so it affects all languages.
It affects every other encoder, so any number of encoders will have a few which do not return rate (the first one will be affected, the second will not).

If you only need distance, you can use the broken FPGA encoder modules for distance only, and not use Rate.
Do you believe an easy work around would be to create twice the number of encoder objects, and stagger the "fake" ones on inputs we don't with the "real" ones, as to only let the fake ones have the broken code, and the real ones get the rates? We do need the rates.
__________________
Attending: MN Duluth Regional