Newer
Older
#### [notes](http://academy.cba.mit.edu/classes/networking_communications/index.html) + [video](https://vimeo.com/415632350)
1. Group assignment: Send a message between two projects
2. Individual assignment: design, build, and connect wired or wireless node(s) with network or bus addresses
This week's class had a lot of new information, so it was quite difficult for me to follow everything.
To understand basics of communication protocols, this [basics of protocols series on circuitsbasics.com](https://www.circuitbasics.com/basics-of-the-spi-communication-protocol) was very useful. For effective communication between electronic devices, they need to use the same language. This language is called communication protocol. Some basic protocols are *SPI, I2C and UART.* These are generally slower than protocols like *USB, ethernet, bluetooth and wifi*, but are ideal for communication between microcontrollers and sensors where the large amounts of high-speed data does not need to be transferred.
Since I do not have access to a lab or a lot of inventory right now, I chose to understand wired communication protocols - SPI & I2C, with Arduino Unos that I do have access to. When I'm in the lab, or get more access to parts, I want to learn about the other wireless protocols too.
While communicating, bits are transferred from one device to another by quick changes in voltage. In a 5V system, O corresponds to 0V and 1 corresponds to 5V voltage.
In parallel communication, multiple bits are transferred at the same time through different wires. Whereas in series, the bits are transferred one after the other through the same wire. The following diagram shows the difference between the two.
### [SPI protocol](https://www.circuitbasics.com/basics-of-the-spi-communication-protocol)
### [UART protocol](https://www.circuitbasics.com/basics-uart-communication/)
### [I2C protocol](https://www.circuitbasics.com/basics-of-the-i2c-communication-protocol/)
I2C communication allows for a single or multiple masters (unlimited) to talk to a single or multiple secondaries (max. 1008). It uses two wires to transmit data between devices. Since it follows series communication, it transfers bits one by one through the same wire.
**SDA (Serial Data)** - to send as well as receive data between the master/s and secondary/s
The clock signal is controlled by the master, and the data is *synchronized* to the bit sampling.
Data is sent in messages. Here is a diagram of the structure of a message.
A pull-up resistor needs to be connected from the Master's SDA and SCL each to VCC, if there are more than one secondaries or more than one masters.
Since I have access to some Arduino Unos, I tried [this guide on Instructables](https://www.instructables.com/Arduino-I2C-and-Multiple-Slaves/) to explore the communication between various numbers of masters and secondaries.
**A5** is SCL
**A4** is SDA
as shown in this [Arduino pinout diagram by pighixxx](https://commons.wikimedia.org/wiki/File:Pinout_of_ARDUINO_Board_and_ATMega328PU.svg).
#### **I2C with one master and one secondary**
[Reference](https://www.instructables.com/Arduino-and-I2C/)
##### Hardware required:
* 2x Arduino Arduinos
* Hook-up wires
##### Circuit:
Using the pinout, I first made the circuit with these steps:
1. Connected GND of both Arduinos.
2. Connected analog pin A5 to A5 (SCL) and analog pin A4 to A4 (SDA).
3. Powered up both Arduinos by connecting them to my computer, and setting the boards ands ports for both.
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
1. Linked to group assignment page
2. Documented your projects
3. Documented what you have learnt fromimplementing networking and/or communication protocols
4. Explained the programming process/es you used
5. Outlined problems and how you fixed them
6. Included design files (or linked to)
