https://firstfrc.blob.core.windows.net/frc2016manuals/TeamUpdates/10.pdf
Um hello G35?
I’m not seeing any actual use for this.
Camera tracking could be considered control, and its possible for an alliance member in the spy box to control the camera of a robot.
I’m seeing this as a huge strategic opportunity.
I’m seeing it as a nightmare for q’ing up.
If something pulses “at 0.5 Hz for 3 seconds” then it pulses 1.5 times.
Edits:
You’re welcome; that’s why I asked.
It will usually be easier for an ASL or other recon signer to learn to use flags or Q-codes in the queue than for a flag signaler to learn enough ASL to be useful.
This will mean a new version of Cheezy Vision.
Robot based control camera for autonomous manual targeting and dive.
:eek:
Aloha!
Probably should be 1 Hz with 50% duty cycle
Yeah it is possible now but that doesn’t make it practical.
Not so fast. G14 still applies.
-G
Quite true… Just remove autonomous from my previous statement.
Seems cumbersome to have a spy controlling the robot, though could be useful since there is potentially many things in the line of sight from the drivers station…
Could be interesting…
I’m sure other people have more grandiose plans, but the main thing I think it will be used for is to tell the robot which way and how far to turn to find a boulder, target, or defense well enough for the driver or semi-auto targeting routines to take over. Something like “boulder at 4-o’clock”.
So I’m thinking the robot can see a spy with a reflective tape hat so they can lock onto the spy. The robot can do simple color matches, so I can see holding two flags (*) below the hat. One with red and green sides, one with blue and white sides. Green forward, red reverse. Blue left, white right. No color, stop. Might mean the spy has to wear a black shirt (**).
Lots of teams working on vision, this may be a time to make that effort pay off.
(*) I was really thinking large ping pong paddles with colors on each side, but flag works too.
(**) Danger is if it sees a Wildstang shirt the robot will break into a happy dance.
EDIT GeeTwo correctly pointed out that G14 does indeed prohibit direct interaction with the robot during Auto.
Thus, my comment below about G14 is incorrect.** EDIT**
It really has my juices flowing!!
EXACTLY THIS!!! Two retro tags held by the Spy to guide the robot.
G14 applies to interaction with the driver’s console, not the robot.
G14 refers to drive teams, regardless of method of interaction.
Q654 confirms that auto is not hybrid in the specific case of a Kinect, but I see no reason to expect an on-robot camera to be any different.
You are correct sir. I have edited my post to reflect this.
Table 2-2: Player Station Light String States and Meanings is gone, and now Table 2-3 Tower Strength Light States and Meanings is the indicator that the field is safe to enter, and the match is in its final 20 seconds.
I had this in the back of my mind when I wrote the Game Manual test.
Time for Rev. 2, a small change. more significant for the Drive Teams and less clutter on the Player Stations.
This may be a problem when a tower is weakened to zero, it may confuse an alliance as to the state of the tower.
Will the whole string blink in the final 20 seconds?
Will the only the top 1/3 blink if the tower has been captured?
IMHO, FMS nightmare.
I hope this adjustment works better than the updated website.
(Sorry, had to get in a dig)
The Game Reveal Video does in fact show the player station lights. My bad.
They’ve known about this since at least this Tuesday, as Danny Diaz (the FIRST engineer doing scorekeeper training this year) mentioned during a training webinar Tuesday Night about this happening. IIRC he mentioned, at the time, that the exact fix hadn’t been determined. Thus, my guess was they found out on Monday and by the time the Tuesday update was ready hadn’t decided on a fix. That said, FMS is still in the works so much that the manual given to us Scorekeepers (and FTAs/FTAAs) isn’t complete yet either, so they still have time to fix it. Compared to other last minute changes they’ve done before, this is pretty minor, at least in terms of FMS.
Since the blue box in G22 hadn’t received any love in this thread, I’m largely repeating my post in another thread… I just want to make sure this didn’t slip by many people!
Have you seen the blue box added to G22 in Team Update 10 (scroll down)? It pretty clearly answers situation B…
I - personally - am disappointed to see this update that came late in the build season (and which flew under my radar until yesterday). We largely avoided designing around scoring from the batter based on concern with being pinned in. This update probably is good for the broader elevation of scoring, but further reduces viable defensive strategies.
Particularly if we end up having trouble scoring as accurately as we need from farther out, we may still be able to use the base of the tower as a “safe” shooting location.
The ambiguity opened up by the potential for non-contact pinning definitely does make this situation (and Wayne’s situation A) more vague and subjective than I like. Hearkens back to some of the 2014 refing woes (although hopefully much less common).