View Single Post
  #21   Spotlight this post!  
Unread 16-12-2016, 23:33
slibert slibert is online now
Software Mentor
AKA: Scott Libert
FRC #2465 (Kauaibots)
Team Role: Mentor
 
Join Date: Oct 2011
Rookie Year: 2005
Location: Kauai, Hawaii
Posts: 334
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: [FRC Blog] 2017 Motor (and Servo?) Controllers and MXP

Quote:
Originally Posted by Basel A View Post
Yeah figured that out about 10 seconds after I posted (that's always how it works of course)
Yes, just to be clear, navX-Micro is definitely legal.

Rather than connect to the MXP port, NavX-Micro connects via USB and I2C and is software compatible with the NavX-MXP libraries. So it's a drop-in addition if you already use NavX-MXP.

Navx-Micro is a great option for teams that have already populated the single RoboRIO MXP port with another MXP board, need a second IMU for turret angle or robot arm angle, or are teams with a limited budget. The 2017 NavX libraries will support multiple NavX-family devices, so you can use both NavX-MXP and NavX-Micro on a single robot - even at the full 200 Hz update rate. And even more, there's upcoming support for video processing latency correction to be released soon.

Last edited by slibert : 17-12-2016 at 02:11.
Reply With Quote