Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Why not use hardware I2C? #14

Closed
nandlab opened this issue Jan 25, 2024 · 1 comment
Closed

Why not use hardware I2C? #14

nandlab opened this issue Jan 25, 2024 · 1 comment

Comments

@nandlab
Copy link

nandlab commented Jan 25, 2024

Hi there,
I looked at your source code and I wondered, is there any reason why you do not use a machine I2C API, for example the I2C class from MicroPython or smbus? Instead you are bit-banging in software.
@Jomarra96
Copy link

Hey, apparently the comm protocol is not quite I2C, as you don't really R/W data into addresses. It's an obscure one, not widely supported. But just check the datasheet for more info

@mcauser mcauser closed this as completed Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mcauser @nandlab @Jomarra96