Thread: ir beacon range
View Single Post
  #6   Spotlight this post!  
Unread 27-01-2004, 01:16
Kevin Watson's Avatar
Kevin Watson Kevin Watson is offline
La Caņada High School
FRC #2429
Team Role: Mentor
 
Join Date: Jan 2002
Rookie Year: 2001
Location: La Caņada, California
Posts: 1,335
Kevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond reputeKevin Watson has a reputation beyond repute
Re: ir beacon range

Quote:
Originally Posted by doy
we have the beacon and receiver code running, and everything seems to be working fine - the beacon output looks correct on an oscilloscope, and the code is running without errors, but the problem we are having now is that the receiver is only recognizing the beacon if the beacon is held directly in front of the receiver at a maximum range of about 4 inches. this is using just the default code, modified so that the beacon and reciever can run on the same frc (we dont have an edu controller). has anyone else run into this problem? ive noticed that most people have been having the problem of their sensors being too sensitive, so i dont know what our problem might be.
As I haven't tried this configuration, I'd suggest sprinkling some debugging printf()s around your code to see what's happining within the Sensor_Stats array. I'd be particularly interested if the beacon data is being discarded because the pulses aren't within the type-0 or type-1 time windows. This would be indicated if Sensor_Stats[n].Invalid_Count was incrementing.

-Kevin
__________________
Kevin Watson
Engineer at stealth-mode startup
http://kevin.org