|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: FTC 2012 RobotC IR Sensor Programming and implementation
Hey Dick.
Check out this doc from a few years back... http://www.usfirst.org/sites/default...icsR2-rev2.pdf The IR seeker is made using 5 discrete sense elements. Each element has an approximate 60 Degree sensitivity area. These also overlap each other by about 5 degrees to form a dusl sense area (beam). This overlap is usefull because it provide a narrow sense area, but there is not one that is centered on the "forward" direction of the seeker. If you want to understand it beter, chek out some related IR seeker links here: http://www.usfirst.org/roboticsprogr...ionalresources |
|
#2
|
||||
|
||||
|
Re: FTC 2012 RobotC IR Sensor Programming and implementation
We were able to find some sample code that shows the 5 signal strengths on the NXT brick. The values seem to go from 0-255. Strangely enough, they show some readings we didn't expect, like having a sort of 'dead zone' in what would be Direction 3.
Again, as a LabVIEW team, we're thoroughly confounded with using this thing for navigation. We're gonna keep plugging away though, and if we get some stuff that works reliably, we'll post the code here. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|