Rule G05 and Autonomous

[yes]

3.2.2.1 G05

When placed on the FIELD, each ROBOT must be:
B. confined to its STARTING CONFIGURATION

So our strategy with Autonomous was that we would place the robot into the optimal shooting position and move it so that it touched the pyramid while gathering data from encoders. The encoder readings would then be flipped and used to move the robot back exactly to the optimal position.

We recently reread the rules and found out that Rule G05 might kill our entire beginning to Autonomous. Can anyone clarify whether we would be breaking Rule G05 with our strategy?

Thanks in advance,
Just another programmer from 2338

[ekapalka]

I sure hope this is legal :D It's an amazing idea!

[dodar]

Originally Posted by yes

3.2.2.1 G05

When placed on the FIELD, each ROBOT must be:
B. confined to its STARTING CONFIGURATION

So our strategy with Autonomous was that we would place the robot into the optimal shooting position and move it so that it touched the pyramid while gathering data from encoders. The encoder readings would then be flipped and used to move the robot back exactly to the optimal position.

We recently reread the rules and found out that Rule G05 might kill our entire beginning to Autonomous. Can anyone clarify whether we would be breaking Rule G05 with our strategy?

Thanks in advance,
Just another programmer from 2338

All that starting configuration means is that your robot cannot be outside its own frame perimeter before the match, be taller than 60", and have a frame perimeter greater than 112".

[MARS_James]

Originally Posted by dodar

be taller than 60", .

Starting configurations definition says nothing about height and considering starting in your own Auto Zone you can be the max height of 84in

[Doug G]

Originally Posted by MARS_James

Starting configurations definition says nothing about height and considering starting in your own Auto Zone you can be the max height of 84in

Off topic I know but I think a lot of team's missed this rule change for this year....

[MagiChau]

When placing the ROBOT on the FIELD it is typical for teams to push it into proper position. However, to record encoder counts would require the robot to be running. This means you would have to wait for your robot to turn on before you can actually finish placing it. I don't think the field crew will like the possibility of how long your team could take to be ready for a match factoring in the ~25 seconds for a robot to be on.

[EricH]

Originally Posted by MagiChau

When placing the ROBOT on the FIELD it is typical for teams to push it into proper position. However, to record encoder counts would require the robot to be running. This means you would have to wait for your robot to turn on before you can actually finish placing it. I don't think the field crew will like the possibility of how long your team could take to be ready for a match factoring in the ~25 seconds for a robot to be on.

G05 is not the issue. G07, delay of game, would factor in, however. Robots that take too long to set up get disabled for the match.

BUT! I have a solution! Presumably, you will know (or can dial in) your optimal shooting position before competition matches begin. Some moving of the robot either manually or with the controls should give you an encoder count to move a certain distance. Namely, the distance between the pyramid and your favorite shooting spot. Input that value into your code as the distance to move, and all you have to do is remember to turn the robot on (and anything else on your prematch checklist).

[Kusha]

This question seems like it would fit this thread, would a tape measure be allowed on the field?

[dodar]

Originally Posted by Kusha

This question seems like it would fit this thread, would a tape measure be allowed on the field?

No measuring devices are allowed on the field by team members.

[XaulZan11]

Originally Posted by dodar

No measuring devices are allowed on the field by team members.

Unless it is part of your robot, right?

[~Cory~]

Originally Posted by XaulZan11

Unless it is part of your robot, right?

Correct, provided you can set up your robot just as fast as all of the other teams. We had a couple of "sighting" holes on our robot last year for starting position and the refs had no problems with us using them.

I am not sure about the legality of this tatic, but the robot could be turned on in the que and you could press a button to start "recording" the encoders when the bot is positioned on the field. Looking in the rules right now.

[Saberbot]

Last year our alignment jig was my left shoe. It doesn't have to be too complicated!

[JesseK]

This autonomous strategy is inherently outside the intent of the rules. The robot would get live calibration data prior to every match to use during the match? Yea, that ain't gonna fly. It's comparable to your drivers controlling the robot prior to autonomous period. It'll also set a precedent that will lead to wonkier rules about what's allowed to happen when a robot is set down on the field.

There's a better way: find a known point to always set down on, then go a known distance in autonomous. If you can't even do this, then your team will be in trouble if you're ever asked to move your starting position in order to accommodate another team's autonomous (e.g. you both shoot 3 from the same spot -- who moves?).

[B Dot]

This question seems like it would fit this thread, would a tape measure be allowed on the field?

When you said tape measure i instantly thought of a range finder, like what bow hunters and even golfers use to measure distances. It would be fairly quick and discrete and there would be less factors for human error

[FrankJ]

Your proposal is not inherently against the rules.

My understanding is the disable just disables the outputs. The program in the crio is still running. So you can have code that monitors the encoders, you just have to stick it the right place so it runs during disable. You could input the start point from the smart dashboard. You can even put a push button on one of the inputs on the robot to mark the zero point of where you start reading your encoders from. Nothing in G05 prevents this.

The only issue would be G07 if you take too much time. A little practice would prevent this.