|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Multiple cRIO/roboRIOs
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
|
|
#2
|
||||
|
||||
|
Re: Multiple cRIO/roboRIOs
But... It's only October... This shouldn't be happening...
READ THE MANUAL!!!!! |
|
#3
|
|||||
|
|||||
|
Re: Multiple cRIO/roboRIOs
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. |
|
#4
|
||||
|
||||
|
Re: Multiple cRIO/roboRIOs
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! |
|
#5
|
||||
|
||||
|
Re: Multiple cRIO/roboRIOs
Quote:
Quote:
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 would be much more efficient option. |
|
#6
|
||||
|
||||
|
Re: Multiple cRIO/roboRIOs
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.
|
|
#7
|
||||
|
||||
|
Re: Multiple cRIO/roboRIOs
Yeah. I guess that that was kind of a dumb question, and maybe I should read the manual more thoroughly.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|