Currently, enabling/disabling the OdomertyFilter in KVHDriveNode will cause it to simply resume where it left off. This is probably not the desired effect. We should require the filter to be re-initialized with a state estimate and covariance upon re-enabling the filter.
Currently, enabling/disabling the OdomertyFilter in KVHDriveNode will cause it to simply resume where it left off. This is probably not the desired effect. We should require the filter to be re-initialized with a state estimate and covariance upon re-enabling the filter.