This shows you the differences between two versions of the page.
lkd:laboratoare:04 [2024/07/11 16:28] daniel.baluta [Practical lab] |
lkd:laboratoare:04 [2024/07/11 16:42] (current) daniel.baluta [Presentation] |
||
---|---|---|---|
Line 4: | Line 4: | ||
==== Presentation ==== | ==== Presentation ==== | ||
- | * follow slides at {{:lkd:laboratoare:lkd_slides_03.pptx| Session 3}} | + | * no slides, all practical |
==== Practical lab ==== | ==== Practical lab ==== | ||
Line 48: | Line 47: | ||
XX - is the address of the I2C device. There are two ways of finding this. You can dig inside the [[https://www.optimusdigital.ro/en/index.php?controller=attachment&id_attachment=4892 | datasheet ]] and confirm the address by scanning for devices on i2c3 node on the hardware. Use ''i2cdetect -y 2''. | XX - is the address of the I2C device. There are two ways of finding this. You can dig inside the [[https://www.optimusdigital.ro/en/index.php?controller=attachment&id_attachment=4892 | datasheet ]] and confirm the address by scanning for devices on i2c3 node on the hardware. Use ''i2cdetect -y 2''. | ||
+ | |||
+ | The datasheet states that the I2C address is as shown as below, but you need to look closer and also understand the output of i2c scan command ''i2cdetect -y 2''. | ||
+ | |||
+ | {{:lkd:laboratoare:i2caddr.png}} | ||
== Step 4 - Load the driver & read the distance measured by sensor == | == Step 4 - Load the driver & read the distance measured by sensor == | ||
Line 72: | Line 75: | ||
</code> | </code> | ||
+ | |||
+ | === Exercise 2 === | ||
+ | |||
+ | Control a motor using GPIOs. Use the following {{:lkd:laboratoare:motorcontrolsetup.pdf| Guide }} | ||
+ | |||
+ | {{:lkd:laboratoare:motor1.jpeg?500}} | ||