Robocoach functions that change as the match progresses??

[bduddy]

Originally Posted by kylelanman

So in terms of how I have it programmed it is fine I just need to make sure I word what each button does on the Index card that lists our functions?

It should be fine-that sounds exactly like what (I think) the GDC intended. On your index card, I would write something like this:

1-Tells robot ball is on left side of rack
2-Tells robot ball is in middle of rack
3-Tells robot ball is on right side of rack
4-Tells robot to drive around track

I don't think anyone will have a problem with that.

[EricH]

Originally Posted by bduddy

It should be fine-that sounds exactly like what (I think) the GDC intended. On your index card, I would write something like this:

1-Tells robot ball is on left side of rack
2-Tells robot ball is in middle of rack
3-Tells robot ball is on right side of rack
4-Tells robot to drive around track

I don't think anyone will have a problem with that.

That would be acceptable by the rules. It's field state information.

You would need to code the robot such that it would know where it was in relation to the Overpass after it turned the corner, but that shouldn't be too hard with a few sensors.

[kylelanman]

Originally Posted by EricH

That would be acceptable by the rules. It's field state information.

You would need to code the robot such that it would know where it was in relation to the Overpass after it turned the corner, but that shouldn't be too hard with a few sensors.

Do you mind telling me what kind of sensors you had in mind. I was planning on relying solely on a timing routine and hoping that we don't get hit by another robot that would mess us up but sensors would be great. I was thinking ultrasonic but I kinda thought that the range wouldn't be high enough to sense sides of the track and what not.

[EricH]

Originally Posted by kylelanman

Do you mind telling me what kind of sensors you had in mind. I was planning on relying solely on a timing routine and hoping that we don't get hit by another robot that would mess us up but sensors would be great. I was thinking ultrasonic but I kinda thought that the range wouldn't be high enough to sense sides of the track and what not.

You choose. I'm not a programmer, but when I program, my weapon of choice is an RCX rotation sensor...

Encoders or infinite-turn pots in the drive would probably work, as would ultrasonic, light sensor, timer... Choose your method.

[SteveJanesch]

We're working on something similar now, but our commands are "Get Ball 1/2/3" and "Stop", with a repeating default of running half a lap. We assume there'll be contact, and want to prevent damage to ourselves or others if possible.

As far as sensors go, we're trying to incorporate a gyro for orientation, wheel coders (with the gyro) to accumulate x,y position on the field, ultrasonic rangefinders looking left and right for position in the lane, and a range finder looking up to detect the overpass. The problem we'll face in incorporating it all is what to believe when - if no 'bots or balls are next to us in the lane, the sum of the rangefinder readings should be 13.5 feet less the width of our robot. That'll happen occasionally at best - the rest of the time the sum will be less, unless we get spun out. Should be interesting.

Steve