|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Driver Station Vision?
Quote:
BTW, lolz: Quote:
|
|
#2
|
|||||
|
|||||
|
Re: Driver Station Vision?
I'm going to go through this once. I may or may not answer questions about the first part of this post. This is another round of FRC History 102: Rules that Changed the Game.
For this episode, we travel back in time to the year almost 10 years ago when autonomous was introduced: 2003. Yep, my first year on a team. I hadn't discovered CD yet, but I've seen some of this sort of thread from way back then. Now, back in 2002 and before, you had 2:00 of driving. Teams would start the match with sticks at full forward on occasion, especially in 2002. Then along comes this 0:15 of autonomous to start that (actually, there were 30 seconds of match play before teleoperated, but that's another story altogether--humans were actually on the field in 2003 during the matches). And so teams started coming up with "Can we use this button on the operator interface to control the robot" scenarios, including using the E-stop, if I recall the threads correctly. FIRST then responded: You must be behind this line to start the match or else (I forget the penalty). Collective "WAAAAAHHHH" from the teams who were discussing this, followed by "How can we reach?" and "But we can't go 3 feet fast enough!" See http://www.chiefdelphi.com/forums/sh...ad.php?t=17122, particularly Dave Lavery's post. Do you see what I'm getting at? Other than the means that FIRST specifically says may be used to control a robot (the IR remotes in 2008 and the Kinect this year, both strictly controlled), if you are controlling a robot in autonomous/hybrid mode with anything other than onboard/on operator console code, you are violating the intent of that mode, and you can bet your rear that the first match you do that in, someone contacts the GDC and says that someone is controlling their robot via non-approved methods. The best you can look forward to is it being ruled legal for the event while the GDC discusses the matter. But then there are rules... Now, the rules. [G19]: Any control devices held or worn by the drivers must not be connected during hybrid. As noted, if you're the control device, via a webcam, then either you or the webcam must not be connected. Your choice. (If you're using special clothing, that would be the control device, put it down on the shelf; not only that but there's other rules dealing with that.) And the largely-unread rules. Quote:
I should also note that using the reflective tape would probably be considered distracting or jamming a robot's vision system, and shut down under those rules. In short, you're violating the spirit, but not necessarily the letter, of the rules. And, in short order, you'd probably find yourself also violating the letter of the rules, when the GDC had time to review. How would you feel if the system that won Innovation in Control was ruled definitively illegal almost immediately, if it wasn't ruled illegal from the get-go? |
|
#3
|
||||
|
||||
|
Re: Driver Station Vision?
There was a team in 2010 that came up with the idea to make a ramp to deflect soccer ball from the input ramp back into their on goal. Dominated their competitions. Not specifically against the rules, but I expect was not something the game committee thought of or intended. I expect this is a similar situation. The camera is part of the allowed devices (no restrictions on operator station computers.) so you can't use [T33]. [G19] applies specifically to worn/held devices which the camera is not. I would be OK with the game committee say the intent of Autonomous (hybrid) is no operator input & saying you cannot do it. Q&A seems to hang on the letter of the rules though. Maybe I will ask just to see the response.
For a variation of a theme has anybody tried voice commands through the op station microphone? |
|
#4
|
|||
|
|||
|
Re: Driver Station Vision?
That would be the coolest thing ever! Unfortunately, it gets pretty loud down there behind the glass.
|
|
#5
|
||||
|
||||
|
Re: Driver Station Vision?
Tell your team they have to chant loudly so the robot will shoot? Might be fun for demonstrations.
|
|
#6
|
|||
|
|||
|
Re: Driver Station Vision?
You, sir, may just have a test subject for your great idea! Let's see in the off season!
|
|
#7
|
||||
|
||||
|
Re: Driver Station Vision?
If you read rule [1.6]
Quote:
|
|
#8
|
|||
|
|||
|
Re: Driver Station Vision?
Alright, first of all, I started this thread just to share what I thought would be a cool idea more than anything. Just putting that out there... Is it realistic? Probably not. But cool? Yep!
Now onto the lawyering: Quote:
By the way, EricH quoted rule T33 awhile back, I'm going to bring that up again: Quote:
Last edited by agartner01 : 30-03-2012 at 14:38. |
|
#9
|
||||
|
||||
|
Re: Driver Station Vision?
The rule says any input (not signalling). Pretty inclusive to me. But I am not the one you have to convince. I don't think you will get much traction with the ref though.
![]() Last edited by FrankJ : 30-03-2012 at 15:42. |
|
#10
|
|||||
|
|||||
|
Re: Driver Station Vision?
Quote:
And, like Frank said, the rule disallows any input from the drivers. Control with hands is input. As I noted before, when talking about the discussion when automode first came out, that would be akin to using the reset button (or appropriate substitute) to control the robot during automode. Unless it is specifically declared as legal, like the Kinect, then I would assume that this method is not legal. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|