Thread: roboRio limited to 8 Analog Inputs
View Single Post
  #4   Spotlight this post!  
Unread 08-02-2015, 23:31
slibert slibert is offline
Software Mentor
AKA: Scott Libert
FRC #2465 (Kauaibots)
Team Role: Mentor
  
Join Date: Oct 2011
Rookie Year: 2005
Location: Kauai, Hawaii
Posts: 349
slibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud of
Re: roboRio limited to 8 Analog Inputs
Quote:
Originally Posted by Joe Johnson View Post
* Looking at the pinouts, it looks like the REV RIOduino passes through all the MXP signals so I may be able to plug the REV RIOduino into the roboRIO then plug the navX into the REV RIOduino. I have two concerns. First, will they even physically fit together (see photo attached). Second, both want to use the UART lines -- The roboRIO TX line is no problem as I can have them both listen without a conflict. But I will have to let one or the other use the roboRIO RX line. Never a dull momemt.
The navX MXP has a few dip switches on it; if the UART switch is moved to the disabled position, the navX MXP will completely stay off of the MXP TTL UART lines.

If the navX MXP UART access is disabled, you can still communicate to the navX MXP via the USB port, or you can use the I2C and SPI interfaces. The Labview navX MXP library supports any of these interfaces, however the Java/C++ navX MXP I2C/SPI libraries are not yet released.
Reply With Quote