![]() |
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? |
| All times are GMT -5. The time now is 00:34. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi