[AllenGregoryIV]

Originally Posted by glennword

Okay, off topic, but r66 was mentioned so I hope this isn't too off base.
My team is currently in the middle of designing a swerve drive. Part of the design is a custom circuit board that would be mounted to each swerve module to reduce the amount of computing the ___RIO has to do, as well as improve modularity, wiring, and ease of replacement if a module were to fail. The board takes inputs from the SideCar (if using 2014 and older control system) or roboRIO itself over SPI. The circuit board then processes the inputs and turns them into PWM motor commands, which are sent to a Talon or other approved motor controller. Does this meet the requirements of R66? It could be interpreted as legal if one thought that the ___RIO was still providing the signals by proxy, or it could be viewed as an entirely separate entity, and therefore illegal. Another thought, with the integration of the various serial communication ports on the roboRIO, as well as the MXP boards, do you think that this rule could be omitted, reworded, or loosened in next years manual?
Thanks and sorry if this is off topic and/or confusing.

This doesn't meet the rule because there isn't anything specifically preventing you from leaving those PWM singles on after the robot is disabled. It's a safety issue for everyone at events.