File tree Expand file tree Collapse file tree 3 files changed +10
-1
lines changed
Expand file tree Collapse file tree 3 files changed +10
-1
lines changed Original file line number Diff line number Diff line change @@ -2,7 +2,8 @@ Lego Port
22=========
33
44The `LegoPort ` class is only needed when manually reconfiguring input/output
5- ports. Most users can ignore this page.
5+ ports. This is necessary on the BrickPi but not other platforms, such as the
6+ EV3. Most users can ignore this page.
67
78.. autoclass :: ev3dev2.port.LegoPort
89 :members:
Original file line number Diff line number Diff line change @@ -3,6 +3,11 @@ Sensor classes
33
44.. contents :: :local:
55
6+ *Note: * If you are using a BrickPi rather than an EV3, you will need to manually
7+ configure the ports before interacting with your sensors. See the example
8+ `here <https://github.com/ev3dev/ev3dev-lang-python-demo/blob/stretch/platform/brickpi3-motor-and-sensor.py >`_.
9+
10+
611Dedicated sensor classes
712------------------------
813
Original file line number Diff line number Diff line change @@ -38,6 +38,9 @@ class LegoPort(Device):
3838 the LEGO MINDSTORMS EV3 Intelligent Brick, the LEGO WeDo USB hub and
3939 various sensor multiplexers from 3rd party manufacturers.
4040
41+ See the following example for using this class to configure sensors:
42+ https://github.com/ev3dev/ev3dev-lang-python-demo/blob/stretch/platform/brickpi3-motor-and-sensor.py
43+
4144 Some types of ports may have multiple modes of operation. For example, the
4245 input ports on the EV3 brick can communicate with sensors using UART, I2C
4346 or analog validate signals - but not all at the same time. Therefore there
You can’t perform that action at this time.
0 commit comments