Closed qhdwight closed 4 years ago
I discovered that the spark takes time to actually set it's value after setPosition
. So, the set odometry routine has to account for this and actually be a timeout routine with delay of like 0.2. Suspect, I know, but we gotta do what we gotta do
Commands.driveWantedOdometryPose
needs to be not null for one cycle inside ofDriveHeadingController
update system.