-
Notifications
You must be signed in to change notification settings - Fork 57
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 16 bit command/index #101
Comments
although we have been able to do some basic comms with i2cWriteSync and i2cReadSync, so probably more for convenience than anything I expect. |
The plain I2C methods described in the readme can be used to achieve what's needed here. For example, for the read shown in Figure 12, call For the write shown in Figure 11, call If needed, your application can implement higher level methods suitable for accessing the VL53L3X which leverage the functionality provided by the plain I2C methods that i2c-bus offers. I won't be adding methods to cover this use case to i2c-bus. The read shown in Figure 12 that first writes to address 0x52 and then reads from address 0x53 isn't very conventional. |
Thanks for getting back so promptly. So we've worked out the 52/53 thing is actually a documentation anomaly. It's actually write/read to 0x29 including the r/w bit (silly way to identify the address in my opinion). Anyway, thanks for this great module and we'll make do with the plain i2c methods. Cheers |
In interfacing with some advanced sensors (e.g. ST VL53L3X) it requires a 16 bit command to identify the register to access. We were wondering if it was possible to add this functionality to this module (which we use extensively thank you).
The text was updated successfully, but these errors were encountered: