View Single Post
  #1   Spotlight this post!  
Unread 25-01-2004, 22:53
Mr. Lim Mr. Lim is offline
Registered User
AKA: Mr. Lim
no team
Team Role: Leadership
 
Join Date: Jan 2004
Rookie Year: 1998
Location: Toronto, Ontario
Posts: 1,125
Mr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond repute
Timer Interrupt 1 and the IR tracker

Quick question referring to the default IR tracker code...

Every time timer interrupt 1 rolls over, it looks like there's enough time in between to detect 2 or 3 occurrances of either beacon.

I lowered the search increment of the trackers to get a more accurate tracking of the beacons, and to avoid missing them altogether, at the expense of tracking speed.

To recoup some speed, it LOOKS like I can shorten timer interrupt 1 to half its current rollover time. It seems like I will get a few ticks back instead of waiting to see a beacon I already know is there.

Has anyone else done this? Or did you have a convincing reason to not do this?