Semi-Omni-Arcade Drive

[Delian]

Our team tried this drive last year and then tested our drivers on an obstacle course filled with Orbit balls and goals. We found that it was far more intuitive to leave out the gyro-relative code. Most drivers found it easier to "throw" their orientation to them being on the robot, rather than relying on a gyro.

[byteit101]

We tested it out last night, and the 2010 KOP Gyro (and Accel) drifts about 1.5-2 degrees a second, ever increasing.
our sensitivity is set to gyro->SetSensitivity(0.007);
Is everyone experiencing this? if so, how do you fix it?

[Greg McKaskle]

If that is with the robot standing still, that sounds too high. I'd suggest repeating the test and make sure that the robot isn't moved while being calibrated, and make sure the modules are plugged in when the cRIO is turned on, and make sure that your wires aren't picking up noise from motors and such.

Greg McKaskle

[byteit101]

Originally Posted by Greg McKaskle

If that is with the robot standing still, that sounds too high. I'd suggest repeating the test and make sure that the robot isn't moved while being calibrated, and make sure the modules are plugged in when the cRIO is turned on, and make sure that your wires aren't picking up noise from motors and such.

Greg McKaskle

The robot was on blocks, not moving (visibly), all 5 modules were plugged in, and the wire went from the crio away from the cims, turning at about .2-.4