added support for device address 0x69#9
Open
shijogeorge24 wants to merge 1 commit intoDFRobot:masterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: Enhance BMX160 Library for Customizable I2C Address Initialization
Description:
Issue: While working with the BMX160 sensor on the Arduino Mega board, I encountered a limitation where using multiple sensors with the default I2C address (0x68) became problematic. The address was hardcoded to _addr=0x68 in the header file, limiting the flexibility for users requiring multiple sensors.
Solution: To address this, I have made modifications to the BMX160 library:
Updated the begin function to accept an optional argument for the I2C address.
Users now have the flexibility to specify a custom I2C address during sensor initialization or use the default 0x68 address if left unspecified.