View Single Post
  #10   Spotlight this post!  
Unread 18-11-2015, 23:02
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Using navX MXP to get robot velocity

Quote:
Originally Posted by slibert View Post
If we back up to the OP's question about velocity for motion profiling (rather than calculating displacement), do you think your test rig showed promise for velocity vector estimation that would rival or exceed encoders?
Errors in measuring position translate directly to errors in deriving velocity.

When we gave up on the "telephoto mouse" project, we went to a trio of encoders (something like a US Digital S1, 64 counts per revolution) mounted to custom-fabricated follower wheels that were built something like the old "trick wheel" omnis. On carpet, they worked very well (though we soon discovered a hardware limitation in the IFI controllers' interrupt support, which we overcame with a simple TTL "quadrature hysteresis" circuit between the encoder and the digital input pins).