[EricVanWyk]

It is really easy to bloat vision code. Before you go through the complexity of adding a second cRIO, I would take a good hard look at your vision code and make sure you can't fix it first.

A common mistake is to put vision and drive in the same loop, which slows the drive code to the same rate as the vision code. They belong in parallel loops, which forces the portion of your drive algorithm that is dependent on vision inputs to accept that they will run at different rates. If you split vision off to a separate cRIO but you do not solve that fundamental issue, you will not see any benefit from the exercise.