Thread: PILOT Signals
View Single Post
  #12   Spotlight this post!  
Unread 19-01-2017, 14:36
rich2202 rich2202 is offline
Registered User
FRC #2202 (BEAST Robotics)
Team Role: Mentor
 
Join Date: Jan 2012
Rookie Year: 2012
Location: Wisconsin
Posts: 1,301
rich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond repute
Re: PILOT Signals

In general, LED's on the robot communication information is not a problem. Otherwise, the RSL and other status lights would violate the rule.

LED's are used all the time to provide robot status to the Drive Team.

In your quote, the issue is: What is "human-originated commands"? If the LED is turning on/off as a result of the Robot Code, it is not "human-originated" even though it might be the result of a human event (pressing a button).

That said, I can't see the benefit of the Driver doing something on the Driver Station to change an LED light on the robot to signal the PILOT - Other than: "Hey, Dummy! Look at the Driver".
__________________


Last edited by rich2202 : 19-01-2017 at 14:43.
Reply With Quote