Smikkelbakje/Drone-FabAcademy-2025
1
0
Fork 0
mirror of https://gitlab.waag.org/make/fablab/interns/2025/sam.git synced 2025-08-02 19:34:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs week 11

Browse Source
This commit is contained in:
Sam Hos
2025-04-04 13:41:48 +02:00
parent 811e58e453
commit e48daca357
6 changed files with 34 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/Assignments/week_11_Networking/image-1.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 94 KiB

BIN
docs/Assignments/week_11_Networking/image-2.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 23 KiB

BIN
docs/Assignments/week_11_Networking/image-3.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 24 KiB

BIN
docs/Assignments/week_11_Networking/image-4.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 21 KiB

BIN
docs/Assignments/week_11_Networking/image.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 89 KiB

34
docs/Assignments/week_11_Networking/networking.md Normal file
View File

@@ -0,0 +1,34 @@
# Networking
For this week I am planning on securing the connection between my drone and the controller since I already have ESPNow running on both and have a stable connection. I wanna make the connection secure so no one can suddenly hijack the drone.
## Group assignment
We used Irja's ESP and my ESP to communicate to each other using the I2C protocol. Henk also gave us his logic analyzer and told us to visualize the I2C and the SPI protocol. We first hooked up the I2C lanes to each other SDA - SDA, SCL-SCL.
We used my old board for this.
![alt text](image.jpg)
After testing and getting no signal for some reason I realized that I desoldered the components and all the bridge resistors to re-use them in another board. So there where no connections running anymore to the mcu. After that we directly hooked it up to the MCU using jumpers.
![alt text](image-1.jpg)
After that we searched for code to communicate I2C between 2 esp's and found this site with exactly what we were looking for.
https://randomnerdtutorials.com/esp32-i2c-master-slave-arduino/
In there were 2 plug and play program to get communication running between the 2 ESP's.
When we had the correct wiring the code instantly worked as expected.
My side. Secondary/child
![alt text](image-2.jpg)
Irja's side. Main/parent
![alt text](image-3.jpg)
Next up was SPI. For SPI we first tried to make the ESP act as a secondary SPI device but we couldn't figure out how to do that and online I also couldn't find anything. After a while Irja found a site that did have some code and documentation on how it worked.
https://circuits4you.com/2019/01/03/arduino-spi-communication-example/
When compiling the main side it worked fine but when compiling the secondary side it had errors that was out of my knowledge on how to fix. So I wen't rummaging through the SPI library in arduino but there wasn't much documentation on how it worked. And the official arduino documentation page gave an error 403.
![alt text](image-4.jpg)