Describe the bug
After connecting a MPU6050 to the regression testing setup today, I noticed that the IMU data streamed back is incorrect (Ay, Az were 0, velocity looked like acceleration, and so on).
To Reproduce
Steps to reproduce the behavior:
Program Robot_F4 into the F446RE. Make sure a MPU6050 is attached
Run soccer_hardware.py in PC Communication
Observe how the last two rows of acceleration data are stuck at 0, while the topmost row of acceleration and bottom 2 rows of velocity appear sensitive to acceleration. (This suggests an 8-byte offset)
Expected behavior
The velocity rows should be sensitive to velocity, and the acceleration rows should be sensitive to acceleration. All should be non-zero, in general, since there is usually noise in the measurements.
Traced this back to #193, it looks like the IMU data offset is being applied relative to the start of RobotState, whereas it should be relative to the start of RobotState.msg:
Describe the bug After connecting a MPU6050 to the regression testing setup today, I noticed that the IMU data streamed back is incorrect (Ay, Az were 0, velocity looked like acceleration, and so on).
To Reproduce Steps to reproduce the behavior:
Expected behavior The velocity rows should be sensitive to velocity, and the acceleration rows should be sensitive to acceleration. All should be non-zero, in general, since there is usually noise in the measurements.
Screenshots![image](https://user-images.githubusercontent.com/20008462/54870302-10390800-4d7b-11e9-942a-9a5d83b9bdd6.png)