View Single Post
  #6   Spotlight this post!  
Unread 19-05-2015, 07:50
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Brownout behavior - alternative design goals

Quote:
Originally Posted by Pault View Post
The issue that 246 and other teams experienced was not that the brownouts were disabling "things," but that in reaction to the brownout the FMS would command the robot to disable.
Quote:
Originally Posted by jhersh View Post
Disabling motors is a totally different thing than being commanded to disable by the field. The FMS is wrong and its behavior will be changed.
Whoops. I missed the fact that Tanis was talking about a software-commanded "disabled mode" instead of the local disabling of actuator outputs. I was not aware that the FMS was even in the loop for brownout behavior.

Quote:
Originally Posted by Tanis View Post
I'm also not sure why a brownout triggers disabled mode (I would think it could continue attempting to run during a brownout).
I'm still not fully understanding the reference to "continue attempting to run", though.
Reply With Quote