View Single Post
  #10   Spotlight this post!  
Unread 02-05-2016, 17:15
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: 337
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: navX Library v2 - From Team 900 - The Zebracorns

Quote:
Originally Posted by Bpk9p4 View Post
is there any difference between the navx-Micro and the navx-MXP
navX-MXP has expansion IO and mounts directly into the RoboRIO MXP port; it has SPI, I2C, TTL UART and USB interfaces. Specifically designed for plug-n-play use in FRC. Great for use as a FRC Chassis Orientation sensor. $99.

navX-Micro is smaller (2x2" square), and only has I2C and USB interfaces. Great for FTC robots, and also placing on arms and cameras on FRC robots if you want to measure their orientation separately from the Robot Chassis. $79.

Other than those differences, the sensor and motion processing firmware is the same.

The RoboRIO libraries (C++, Java, LabVIEW, Python, C#) will work with either, no code change required except to specify which interface to connect to it with.

We are aware of teams who are using both simultaneously on a FRC robot, which is also supported.

- scott

Also, please note that there's currently an issue w/reconnecting to the RoboRIO if communicating over USB if the navX-device gets reset. Kauai Labs is currently working with National Instruments to resolve this issue, but until it is resolved, we are not actively encouraging using the USB interface in competition settings. We'll notify the FIRST community once this issue has been resolved.

Last edited by slibert : 02-05-2016 at 19:26.
Reply With Quote