About nijin_26

Hi. After testing, I confirm that the error was due to data distortion over long cables while using the i2c protocol. I resolved the error by using an i2c bus extender circuit. Thanks for the support and analysis. ... View more

Hi, Thanks for your support. I believe that the data is affected because of the length of the cable I am using. I noticed that I get good values with shorter cables, but with longer cables (>1 m), the data gets corrupted. I would re-confirm this experimentally and update this post with my findings. ... View more

Hi, Thanks for the data. It is interesting to know that -0.06 corresponds to a meaningful value and is not an error code. I plotted your data, and I see that you achieve smooth plots for all angles. Here, I've plotted the roll. There are no outliers.   However, in my case, these values occur at unexpected points, standing out as clear outliers.    In the absense of these outliers, the plot should have looked nearly sinusoidal, as below: This is leading to loss of meaningful information, for example, in the range of 150 to 200, in my plot above. Hence, simply filtering out the outlying points is not a solution. Do you know why this might be occuring? Thanks. ... View more

The Fusion mode used was NDof. I am not sure what you mean by the FW version value.  Data was streamed using Arduino IDE at approx 10 Hz, and the data registers for Euler hrp, Gyro xyz and Acceleration xyz were respectively read using the library functions bno055_read_euler_hrp(&Eul_data_vector), bno055_read_gyro_xyz(&Gyr_data_vector) and bno055_read_accel_xyz(&Accel_data_vector). The values were then type casted to float and divided by 16.00 The following is the screenshot of the log, where the outlier values are clearly seen.   ... View more