mirror of
https://github.com/pybricks/pybricks-api.git
synced 2026-09-12 17:46:19 +00:00
David Lechner
3dad15ac11
We generally shouldn't be raising OSError from user code since it represents an error the bubbles up from the OS. Also, when handling an OSError, we almost always want to check for a specific error code.
24 lines
645 B
Python
24 lines
645 B
Python
#!/usr/bin/env pybricks-micropython
|
|
from pybricks.hubs import EV3Brick
|
|
from pybricks.iodevices import I2CDevice
|
|
from pybricks.parameters import Port
|
|
|
|
# Initialize the EV3
|
|
ev3 = EV3Brick()
|
|
|
|
# Initialize I2C Sensor
|
|
device = I2CDevice(Port.S2, 0xD2 >> 1)
|
|
|
|
# Read one byte from the device.
|
|
# For this device, we can read the Who Am I
|
|
# register (0x0F) for the expected value: 211.
|
|
if 211 not in device.read(0x0F):
|
|
raise ValueError("Unexpected I2C device ID")
|
|
|
|
# To write data, create a bytes object of one
|
|
# or more bytes. For example:
|
|
# data = bytes((1, 2, 3))
|
|
|
|
# Write one byte (value 0x08) to register 0x22
|
|
device.write(0x22, bytes((0x08,)))
|