Quote:
Originally Posted by Tparbotmail
The question I have is can this work well with the other classes, like arcade.
|
The feedback that you get from a quality gyro can be used in many different situations. For our 2014 bot, we used the yaw data from a Nav6 (the predecessor to the NavX) in
our 2-ball autonomous routines; this was a 6WD bot that used a custom version of arcade drive (shout out to Team 254). Our bot drove straight that year, so we didn't need to use it to correct for a drive-train that listed to one side or the other. However, in 2015, we used the yaw data from the Nav6 to drive straight when we wanted to and to strafe perfectly sideways when we wanted to; this was a 5-wheel omni drive system (holonomic drive). While these goals can be achieved with any quality gyro, we like the way that the Nav6 performed, so we have decided to move on to the NavX this year and in future years. You can look at our
codebase (sorry for any trouble deciphering it) to see how we used it, but the important takeaway is that the Nav6/NavX is a quality sensor that can enable your bot to determine its orientation relative to the field throughout a 2:30 match, regardless of which type of drivetrain you use. The promotional materials emphasize certain drivetrains because you can get really interesting behaviour out of a mechanum or swerve drive when you incorporate a gyro; however, it is useful in a variety of scenarios. (We also used the Nav6 to achieve field-centric control on a summer project that has a swerve drive.)
TL;DR: if you want quality yaw data, this is a great sensor that has minimal drift over the course of an FRC match. It doesn't matter what drivetrain you use; we have used it (with great results) on a 6wD, an omni drive (H-drive), and a swerve drive. The only thing that we actually haven't used it on is a mechanum drive (which might be next...but definitely after 2016).