Yaw resets to previous value about esp32 HOT 6 OPEN

On Mon, Jan 15, 2018 at 3:12 PM, Adam ***@***.***> wrote: In your example Im having some odd values with the software Yaw, if it reads 90 and I move it to 180 it will count back down to 90 again..So no matter where I rotate the sensor it resets to what ever value it starts with The hardware Yaw seems to keep its values however. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qrfa51IgJeWum2d6i2NbN_0Akvgfks5tK9trgaJpZM4RfDKu> .

On Mon, Jan 15, 2018 at 3:48 PM, Adam ***@***.***> wrote: shamefully one from china, BNO055 SW Revision ID: 3.11 [image: gy-bno055-9dof-9-axis-bno055-absolute-orientation-imu-ahrs-breakout-sensor-accelerometer-gyroscope-triaxial-geomagnetic] <https://user-images.githubusercontent.com/34798557/34965778-00da1430-fa57-11e7-9edf-2a9badf67630.jpg> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qubR94UlwnwXBK1zQxfgUi4TX2cHks5tK-PhgaJpZM4RfDKu> .

The probelm is in my code, for some reason, the magnetometer data are not updated properly unless using the AMG mode, I think, where just the sensor data are returned. When the fusion engine is used these data seems to be messed up, don;t know why. Just use the hardware solution, you don't need the software solution unless you are doing the fusion on the host for some reason. No reason to use both. On Mon, Jan 15, 2018 at 3:48 PM, Adam ***@***.***> wrote: > shamefully one from china, BNO055 SW Revision ID: 3.11 > [image: > gy-bno055-9dof-9-axis-bno055-absolute-orientation-imu-ahrs-breakout-sensor-accelerometer-gyroscope-triaxial-geomagnetic] > <https://user-images.githubusercontent.com/34798557/34965778-00da1430-fa57-11e7-9edf-2a9badf67630.jpg> > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#13 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AGY1qubR94UlwnwXBK1zQxfgUi4TX2cHks5tK-PhgaJpZM4RfDKu> > . >

On Tue, Jan 16, 2018 at 2:37 AM, Adam ***@***.***> wrote: ok now that makes sense:) I had thought for some reason the hardware values were not fusion values. and yeah the board is ugly and Im not even sure what that other part is with EAUC. Thanks a lot for your help hopefully I have a nice robot video soon and can share it with you:))) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qiWpC3gc3W2MK0nRTCaChrHrNjLaks5tLHv2gaJpZM4RfDKu> .