Multiple cRIO/roboRIOs

[yash101]

I don't see why it would be needed, but are multiple cRIOs, daisy-chained allowed on the robots? Having tons of sensors and motors, you may get stranded with not enough I/O

[Pault]

But... It's only October... This shouldn't be happening...

READ THE MANUAL!!!!!

[Nate Laverdure]

RTM
You forgot to add the BIG DISCLAIMER: Last year's manual applies only to last year's game. We won't know the 2014 rules until 2014.

That said, this particular rule has been around for a while. Devyash, look at <R55> (and the blue box immediately following it) in the 2013 manual.

[cgmv123]

If you have too many sensors/motors, you don't need another cRIO. You're allowed a second Digital Module/Digital Sidecar in your first cRIO.

Instead of additional sidecars, the new RoboRIO has a custom electronics port that can be whatever you need it to!

[RyanCahoon]

Having tons of sensors and motors, you may get stranded with not enough I/O

If you have too many sensors/motors, you don't need another cRIO. You're allowed a second Digital Module/Digital Sidecar in your first cRIO.

Instead of additional sidecars, the new RoboRIO has a custom electronics port that can be whatever you need it to!

Definitely the additional sidecar for motors and digital I/O. If you're using more than 20 motors and 28 GPIO pins, you may want to rethink your robot design. It will be very unmaintainable, at the least.

If you need more pneumatics control channels, you're allowed a second pneumatics module as well, or you can use the relay channels on the DSC to control spikes.

For analog I/O, an I2C I/O expansion board (http://www.adafruit.com/products/1085) would be much more efficient option.

[FrankJ]

The second CRIO would not help much on the outputs anyway. By rule the primary would control all outputs. I don't see that changing with the 2014 rules.

[yash101]

Yeah. I guess that that was kind of a dumb question, and maybe I should read the manual more thoroughly.