Kinect in auton allowed

[TheMadCADer]

Does a Kinect on the Driver Station have to be pointed at the drivers? I'm currently looking for a rule that prohibits directing it at the field and using it as a sensor for the robot that isn't on the robot. Somehow I have a feeling the GDC wouldn't approve of this...

Who knows? Maybe it could be useful. Pathfinding, maybe?

[Hjelstrom]

Originally Posted by TheMadCADer

Does a Kinect on the Driver Station have to be pointed at the drivers? I'm currently looking for a rule that prohibits directing it at the field and using it as a sensor for the robot that isn't on the robot. Somehow I have a feeling the GDC wouldn't approve of this...

Who knows? Maybe it could be useful. Pathfinding, maybe?

the Kinect only senses out to about 12 ft so it wouldn't be able to see the whole field at once. Neat idea though!

[dellagd]

Were probably gonna use it for fun, but maybe for autonomous sequencing. Literally just like a button.

Raise/lower hand to proceed to the next item in your auton for spacing out when your alliance shoots.

[Johnbot]

True autonomous is better than a Kinect-driven "Hybrid" mode, but it is definitely not something to always dismiss, because it can (read: has a small-ish chance of us considering it to) be useful.

Take our current plan for using it, for instance:

The SmartDashboard accesses the Kinect. It takes a photo of them, and then uses the Kinect bone coordinate data to turn said photo into a paper doll of the person using the Kinect.

Then, it keeps updating the drawn parts of the paper doll to match the driver. The SmartDashboard then draws a sword in the driver's paper doll's hand, and starts shooting bombs at the driver's paper doll. The driver must chop the bombs, or he/she will be hit and blow up. The goal will be to last through all of auton.

This works well, as now we can do something while we wait for field issues to be resolved

[nighterfighter]

Originally Posted by Johnbot

True autonomous is better than a Kinect-driven "Hybrid" mode, but it is definitely not something to always dismiss, because it can (read: has a small-ish chance of us considering it to) be useful.

Take our current plan for using it, for instance:

The SmartDashboard accesses the Kinect. It takes a photo of them, and then uses the Kinect bone coordinate data to turn said photo into a paper doll of the person using the Kinect.

Then, it keeps updating the drawn parts of the paper doll to match the driver. The SmartDashboard then draws a sword in the driver's paper doll's hand, and starts shooting bombs at the driver's paper doll. The driver must chop the bombs, or he/she will be hit and blow up. The goal will be to last through all of auton.

This works well, as now we can do something while we wait for field issues to be resolved

So a game within a game?

I like it.

[Johnbot]

Originally Posted by nighterfighter

So a game within a game?

I like it.

That's the idea

[StevenB]

I thought the driver station and/or control system was designed so that no joystick inputs were sent during autonomous mode. Has it changed since my day?

[engunneer]

I think they do allow data to pass from the driver station to the robot. One example is using the driver station to do vision processing off-board.

[Johnbot]

Originally Posted by StevenB

I thought the driver station and/or control system was designed so that no joystick inputs were sent during autonomous mode. Has it changed since my day?

I don't think joystick data is sent, but as the Kinect handled uniquely, it is still sent over.