[Daniel_LaFleur]

Originally Posted by JPruim

I have heard like, 6 different thoughts on Co-Processors, i.e. an Arduino to handle other functions, ranging from an "Absolutely!" to a "Absolutely not.", and from what I gather, the Co-Processor has to

• Not drive the bot
  

• Correct. A co-processor may not directly control ANY output (not just the drivetrain). It may issue commands to the cRIO to execute drive functions.
  

  Originally Posted by JPruim

  Talk to the cRIO about any driving

  ... or any outher output it wishes to activate.
  

  Originally Posted by JPruim

  Disable when Kill Switch is hit

  Not entirely true. All motor outputs must disable when the e-stop is pressed. Since the outputs are all controlled by the cRIO, your coprocessor does not need to be disabled.
  

  Originally Posted by JPruim

  Be powered off the Bot's power supply

  If it is a COTS item, and normally contains it's own battery (like a laptop, for example) it need not run off of the robots battery. That being said, it will be scrutenized closely for safety and other rules compliances.
  

Originally Posted by JPruim

Is my list correct? I'm thinking about dealing with the Computer Vision on a Co-Processor and not get asked to remove it.

One last caveat. All of my answers are based on last years rules. This years rules may be different. Check the rules, when they come out, for compliance.