2020 Team Update 6

FIRST General Forum
1

Really minor, I think:

  • If FMS can’t tell which color the Control Panel is currently on when it needs to pick one, it’ll just pick a random color.
  • Fix rule reference typo in 4.7’s blue box (Thanks, that one had been annoying me much more than it should have.)
  • R16: During events, you can’t practice with your bot at all outside of pit hours, in addition to not “working” on it. (Presumably being clarified due to question asked in Q197.)
1 Like
2

This raises the question whether we have to worry about the CONTROL PANEL sensor might read “not a valid color” while we are attempting ROTATION CONTROL or POSITION CONTROL. What happens then?

1 Like
3

In theory, it’d only read unknown when “between” colors, so I assume if the data it receives goes Red → Unknown → Green then the FMS programming will treat that as the appropriate eighth-of-a-turn.

I’m guessing this is just due to them making sure to cover all the bases in the FMS code, where they don’t want it to crash or anything, so they programmed this in, and then figured it ought to be documented in the manual.

The people who work on FMS are pretty smart; this should be pretty far down on the list of concerns about field operation this year.

3 Likes
4

Just like the hooks in 2017??? :upside_down_face:

4 Likes
5

Hooks are hardware, FMS is software.

I’m all for clean color designation, might end up being a half a pizza slice off what is needed.

6

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.