Thread: navigate code
View Single Post
  #2   Spotlight this post!  
Unread 02-02-2004, 18:26
Kevin Karan's Avatar
Kevin Karan Kevin Karan is offline
Linux Guy
AKA: maxdamage
None #0174 (Arctic Warriors)
Team Role: Alumni
 
Join Date: Jan 2003
Location: Liverpool, NY
Posts: 141
Kevin Karan will become famous soon enoughKevin Karan will become famous soon enough
Send a message via AIM to Kevin Karan
Re: navigate code

Quote:
Originally Posted by AlphaOmega870
how exactly does the navigate code work?
We can't figure out where to put the sensors
Do we put one in input 7 and the rest in 1,2,3, and 4 respectively?
Does the sensor in 7 detect the beacon type and 1,2,3, and 4 home in on it?
Thank you in advance.
The default tracker code is actualy very dumb. First it locates the beacon by scanning. The way it finds it is when both sensors on an "eye" finds it, it assumes its dead ahead. When both "eyes" find it, it assumes its there, turns the robot to face it and drives. If it looses it, it stops then scans again. This is actualy a very poor way to do things. If you have good enough programers, you can make it constantly scan and compare and have a more accurate possition. The only problem is that the default code includes no trig functions and you will have to program your on.
On the subject of possitioning, if you use the default tracker code, you could put them pretty much anywhere, though you may need to do some tweaking of speed and sensitivity. The code has comments that tell you where to plug in the sensors too. Its actualy ports 3-6 by default. Seven is actualy defaulted to a switch that chooses what beacon to home in on. The way it works is both beacons emit a different signal (I cant remember what one is which) and the port 7 toggel chooses what one to follow and what one to ignore.
__________________
It isnt ALWAYS the programmers falt!
2004: Buckeye team website award
2002: Rutgers semi-finalists
2001: National semi-finalists
2001: Rutgers semi-finalists
1998: Manchester Rookie All-Star Award