Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
gy91 mpu9255 and new ak8963
See original GitHub issueUsing a gy-91 which contains a mpu9255 and a different model AK8963
Changed in AK8963.init
if 0x48 != self.whoami:
to
if self.whoami not in (0x48,0x5F):
in AK8963.magnetic (was getting the same y an z values, appears you can no longer read six bytes at a time but must read 2 bytes for each of hxl, hyl, hzl)
So changed
xyz = list(self._register_three_shorts(_HXL)
to
x = self._register_short(_HXL)
y = self._register_short(_HYL)
z = self._register_short(_HZL)
xyz=[x,y,z]
and in mpu6500.init
if 0x71 != self.whoami
to
if self.whoami not in (0x71,0x73)
Still working away trying to get this working …
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You mean this? Looks quite interesting board. Let me know how it goes.
Getting better data using
i2c = I2C(scl=Pin(21), sda=Pin(22), freq=100000). There appears to be an issue with the default freq on an ESP32 communicating with the GY-91. Might be a timing issues?