-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for MPU6052C #10
base: main
Are you sure you want to change the base?
Conversation
Thanks for your contribution. Have you found more information about this IMU ? Is it having a DMP ? |
ok it seems it has a DMP based on this datasheet |
I did some checks now, but there is something I don't understood. The old code seems to work on the STM32F103C8T6 and a MPU6052C IMU. So your fix is actually specific to boards with GD32F103C8T6 chip and MPU6052C IMU ? I also tried a board with a GD32F130C6T6 chip and a MPU6052C IMU by flashing the firmware by the other repo, reading the angles is also worked well. |
You are right, I had this issue on gd32f103c8 with mpu6052c, I don’t have
stm32 with 6052c
So, this fix is specific to this combination
Btw, it’s not mentioned in the datasheet that 6052c has self test feature
Have you tried self test option gd32f130 with mpu5052c?
…On Mon, Apr 18, 2022 at 10:35 AM Candas1 ***@***.***> wrote:
I did some checks now, but there is something I don't understood.
The old code seems to work on the STM32F103C8T6 and a MPU6052C IMU.
With a GD32F103C8T6 chip and a MPU6052C IMU, when displaying the euler
angles with debug variant, the loop is slow and the angles are all zero,
but your commit fixes this.
So your fix is actually specific to boards with GD32F103C8T6 chip and
MPU6052C IMU ?
I also tried a board with a GD32F*130*C6T6 chip and a MPU6052C IMU by
flashing the firmware by the other repo, reading the angles is also worked
well.
—
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQOUEGJQTKOAI55YJBYFHDVFVXKFANCNFSM5TTQWPAA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
No description provided.