You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/hardware/02.hero/boards/uno-r4-wifi/tutorials/qwiic/qwiic.md
+2-24Lines changed: 2 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,31 +27,9 @@ You'll learn what Qwiic is, as well as how to set it up and get started making y
27
27
28
28
## I2C
29
29
30
-
We'll go over the conceptual level of how I2C works, if you want to skip ahead you can [click here](#qwiic)to jump directly to the Qwiic section
30
+
I2C is the communication protocol that is used in Qwiic, it is a protocol that allows you to connect many peripheral devices to a single controller board, using only two pins.
31
31
32
-
I2C is a communication protocol that lets you connect multiple I2C compatible devices in a line, using only two pins that are referred to as SCL and SDA.
33
-
34
-
Each device in the I2C line is functionally independent from the controller, but will respond with information when prompted by the controller.
35
-
36
-
All devices on the line have an address that is represented by 7 bits. With 7 bits you can create 128 unique combinations, and that means that the theoretical limit of the amount of I2C devices a single line can support is 128.
37
-
38
-
An I2C message on a lower bit-level looks something like this:
39
-
40
-

41
-
42
-
- The controller sends out instructions through the I2C bus on the data pin (SDA), and the instructions are prefaced with the address, so that only the correct device listens.
43
-
- Then there is a bit signifying whether the controller wants to read or write.
44
-
- Every message needs to be acknowledged, to combat unexpected results, once the receiver has acknowledged the previous information it lets the controller know, so it can move on to the next set of bits.
45
-
- 8 bits of data
46
-
- Another acknowledgement bit
47
-
- 8 bits of data
48
-
- Another acknowledgement bit
49
-
50
-
But how does the controller and peripherals know where the address, messages, and so on starts and ends? That's what the SCL wire is for. It synchronises the clock of the controller with the devices, ensuring that they all move to the next instruction at the same time.
51
-
52
-
However, you are nearly never going to *actually* need to consider any of this, in the Arduino ecosystem we have the [Wire library](https://www.arduino.cc/reference/en/language/functions/communication/wire/) that handles everything for you.
53
-
54
-
But what does all of this have to do with Qwiic?
32
+
To learn more about I2C and how it functions, check out our [I2C guide](/learn/communication/wire#tutorials).
55
33
56
34
## Qwiic
57
35
Qwiic is an ecosystem of breakout-modules and development boards with a so called Qwiic connector. The Arduino UNO R4 WiFi has one, for example. The Qwiic ecosystem combines the flexibility of I2C with the ease of use of pre-bundled cables making it incredibly easy to create lines of I2C devices, by collecting all the pins to get up and running with a large network of I2C devices in a single cable.
0 commit comments