Hey,
I’m just wondering what teams are using for the 4 functions of the autonomous mode. Right now, we’re deciding whether to use pre-programmed functions or just controlling it like a normal contoller. What are your guys thoughts?
selecting between 4 different auto modes… (pending on where the ball is)
Ummmm im not sure what my team is doing but i’ll check in on it.
is anyone using simple 4-way directional controls? is this a good/bad idea? what are the advantages/disadvantages?
I think the control will be extremely hard using just 4 directions, because you’ll have a hard time getting a signal to your robot. (With all the other IR signals & with the distance and stuff) I think we are going to do the position of the balls thing… Otherwise it’s just going to be a normal autonomous mode.
I was thinking though, what are some suggestions for sensors to tell where you are on the field? We tried the accelerometer & that didn’t work, even with a bunch of filters and some tricky software stuff… Now I’m thinking ultrasonics, cuz that would help with navigating the course too. Then there’s the obvious encoders, but there’s gotta be a better way, right?
I’m going to advise against attempting to have your robocoach try to drive the robot because of the potential interference issues. Here’s the ongoing discussion of why: http://www.chiefdelphi.com/forums/showthread.php?t=62775
I tried to suggest that function 1-4 each access option menu 1-4 with each having 4 functions, but apparently that would be illegal. 
We’re just doing a forward, left, right, stop, thing.(and maybe a lift-the-arm command)
For now, due to fairly high rates of uselessness of the IR reciever board in multi-remote environments, nothing, nothing, nothing and nothing. Fully autonomous right now (with adaptive ultrasonic cruise control :] ).
I’ll write the IR into the robot in case it becomes viable (point wise) to knock the ball off. But since making half a lap in autonomous is worth the same as the ball… :rolleyes:
-q