View Single Post
  #5   Spotlight this post!  
Unread 19-01-2016, 17:37
Jonathan L. Jonathan L. is offline
Programmer alumnus, mentor, and CSA
FRC #1094 (Channel Cats)
 
Join Date: Jan 2013
Rookie Year: 2011
Location: St. Louis MO
Posts: 77
Jonathan L. is a jewel in the roughJonathan L. is a jewel in the roughJonathan L. is a jewel in the roughJonathan L. is a jewel in the rough
Re: navX 2016 Software Reset Displacement

Quote:
Originally Posted by slibert View Post
If you have verified that the navX-MXP is firmly mounted to the robot (i.e., conceptually it should be part of the mass of the robot frame) as described on the RoboRIO installation page, then you've likely achieved the performance limit.
I'm pretty sure this is our problem. The roboRIO and navX are mounted on rubber shock absorbers and attached with Velcro.



Quote:
Originally Posted by slibert View Post
Since you mentioned zeroing the velocity, you may be attempting to integrate velocity to derive a displacement estimate. If you are indeed attempting to integrate the navX-MXP velocity estimates your results on average will be worse than if you use the displacement estimates calculated by the navX-MXP.
I am using the displacement values calculated by the navX. What I meant was, by running the "Z900_navX_Set_Zero_Velocity.vi" subsequent returned values were zero until the system was rebooted.
Reply With Quote