![]() |
Scoring of rotors
If a team gets a rotor in autonomous, they will get 60 points. However, at the end of teleop, will the rotor get scored again for 40 points, for a total of 100? Or does the rotor only get the 60 points from auto?
|
Auto Rotor Point Total?
The rules say that it is 60 points "for each rotor turning by period's T=0" in auto, and 40 points "for each rotor turning by period's T=0 in teleop. Does this mean that a rotor can/would count for 100 points as it would be rotating at the end of auto, and the end of teleop?
Example: One rotor is turning by the end of auto = 60 points Four rotors are turning by the end of teleop = 40 points/rotor = 160 points 60 points + 160 points = 220 rotor points Maybe we're just missing something in the rules . . . Thanks FRC community!! |
Re: Auto Rotor Point Total?
What I got out of the video and of the rules is that you only get the points when the rotor was started initially (after 3 full rotations in the airship.)
Example: You get one rotor activated in Autonomous= 60pts -then there are only 3 rotors left x 40pts = 120pts (that's if you activate the rest during teleop.) So in this case, the maximum points due to the rotors is 180pts (60 during autonomous, and 120 during Teleop.) This is what I got out of it, please let me know if I am wrong Thanks, Dillon |
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
3.2.1, page 23, is pertinent.
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
The only problem is how likely are there going to be three robots able to go to three serperate lifts and have enough time to get rotor 1 to turn? It would probably end up counting as a teleop rotor turn if it takes more than 15 seconds and only give you 40 points like I said in the first example. So it would equal out to the same amount of points either way. |
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
So are teams legally able to grab another gear during autonomous? We would love to put the first gear and then go backward to the loading station and grab another.
|
Re: Scoring of rotors
Good question. I'm sure the answer is going to be, "However FMS is programmed to score it." And I'd guess it would be scored either 60 or 40, not both.
But if a ROTOR is turning at time T=0 of Auto, then it's also turning at time T=0 of Teleop. So technically it should count both, per Table 4.1. Unless FMS turns off any turning ROTOR at the end of Auto. Q&A will be the only definitive answer. Edit: I'm pretty sure it would have to be one or the other, not both. Else the FUEL scored in Auto would also count again in Teleop. |
Re: Auto Rotor Point Total?
Quote:
This will be tricky and unlikely, but not impossible. |
Re: Auto Rotor Point Total?
I think we'll see 120 pt. rotor scores in auto from some playoff alliances. Likely with each robot hanging a gear.
|
Re: Scoring of rotors
Two similar threads merged, resulting in somewhat out of order posts.
|
Re: Scoring of rotors
There are stack lights for the first three rotors that are meant to indicate if each rotor was engaged in auton. I assume (I know, bad idea) FIRST would not put a stack light on the second (or third) rotor if they did not expect it to be spinning at the end of autonomous at least once.
|
Re: Scoring of rotors
As far as our team currently understands it:
Rotors are scored if they are turning at T=0 of a period (per the scoring chart on page 42 of the manual). They are not scored when they start turning. An indicator is on the first two rotors (as per page 23 of the manual) because they are the only two which can possibly be powered during autonomous (maximum of 3 gears can be lifted during auto). There is however, no discussion of that indicator causing such a rotor to not be scored at the T=0 of the tele-op period. In our thoughts (but we wait for some official decision), the score for such a rotor is as follows: Autonomous ends (T = 0) -> 60 points per rotor spinning Tele-op ends (T = 0) -> 40 points per rotor spinning. Each rotor started in auto is effectively worth 100 points by the end of the match. Making the maximum points for engaging rotors 200 (auto, 2 rotors) + 160 (tele, 4 rotors) + 100 (playoffs bonus) or 1 RP (quals bonus), for 460 points, or 360 points and an RP. Note, the logistics of powering the 2nd rotor during autonomous: not only must you deliver all 3 gears to their lifts, the 2 pilots must then lift the 3 gears and place them properly (this means one pilot must lift 2 gears within 15 seconds, safely) then make 3 rotations of the second rotor. This process must be complete within 15 seconds, as the rotor must be spinning at T=0 of auto. [b]TL : DR[\B] - as of current rules, 60 points for auto + 40 points per tele-op, even if it started spinning during auto = 100 points. Can get 2 rotors during auto, but very difficult in the time limit. |
Re: Scoring of rotors
Quote:
as far as quickly and safely lifting three gears, I also suspect that an update will be made requiring the pilot to drop the lift back down before placing the gear. this is slower, but is a tripping hazard. otherwise the faster thing to do is not reset the lift until the beginning of teleop. |
Re: Scoring of rotors
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
Is there some magic happening that I don't see? :) |
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
The closest I can find: Quote:
|
Re: Scoring of rotors
HUMAN PLAYER practice will be a must. Perhaps once people get a AIRSHIP model completed with LIFTs, they will share on youtube the possibility of the 380 point teleop score for more buy in.
Is it safe to say that the Robot can not push the lift up? I see a statement that reflects that it is to be pulled up by the player. But Robot interactions do not exclude pushing field elements. I see this as a potential safety issue as a GEAR could be moving up without the PILOT's direct manipulation, however students may think it saves the pilot time by having the robot lift up the gear for them. |
Re: Scoring of rotors
I tried looking through the field assembly...
It it about a 2.5 ft cable pull to get the gear from the bottom of the LIFT to the PORT? |
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
|
Re: Auto Rotor Point Total?
Quote:
I do wish that the manual didn't say the GEAR sets "engage the corresponding rotor." That implies to me that the GEAR sets are physically meshed with the rotor, when the field tour explains that the GEARs drive an encoder, which tells the FMS to turn on the rotor. |
Re: Auto Rotor Point Total?
Quote:
|
Re: Scoring of rotors
If they do not change the rules, a team could take the reserve gear and put it into the first Rotor. This would get them the 100 points but because the other alliance to also get 25 points which means that the alliance would net 75 points, which is greater than the 40 they would get if they waited for teleop.
|
Re: Scoring of rotors
Quote:
That being said, I am almost certain that the rules intended for autonomous rotors to be 60 points total, not 60 then 40. This would make the tech foul for taking the reserve gear and powering a rotor more of a penalty than the point bonus for getting an auto rotor. (you get 20, they get 25). |
Re: Auto Rotor Point Total?
Quote:
|
Quote:
Interesting idea, although I'd definitely check the Q&A for legality. |
Re: Scoring of rotors
https://firstfrc.blob.core.windows.n...amUpdate01.pdf
The team update states that rotors are scored only if they are not previously scored, so I interpret this as a rotor scored in autonomous won't be recounted for teleop. Quote: For each ROTOR turning by period’s T=0, that’s not previously been scored |
Re: Scoring of rotors
From today's Team Update 1:
Quote:
|
| All times are GMT -5. The time now is 03:44. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi