Compare commits

...

3 Commits

Author SHA1 Message Date
7540575c64 Final project progression on way to control the drone 2025-03-04 16:55:53 +01:00
866dcd6ab2 Final project 2025-03-04 15:58:43 +01:00
64e15dcd60 electronics rambling about design rules 2025-03-04 13:18:16 +01:00
13 changed files with 82 additions and 2 deletions

View File

@@ -160,6 +160,24 @@ It could be prettier if I used 2 layered board. I learned using the KiCad manual
Like this!
The blue trace is going under the red one using a via.
When running the design rules checker I got a lot of errors that my silkscreen text was overlapping on the solder mask.
![alt text](image-38.jpg)
That means that the text is overlapping the soldering. So I need to fix that by dragging the components a bit away from each other. Or deleting the silkscreen letters.
There are also some issues I can't fix. For example these pads keep giving errors because they are under the xiao but they are part of the xiao so I can't fix that.
Now I'm going to make edge cuts. Edge cuts are the shape of the pcb.
![alt text](image-39.jpg)
I ended up using [this youtube tutorial](https://youtu.be/aHIIXjRAhZA) to create the rounded edges. One thing I noticed is to stay on the big grid lines. It makes life a lot easier when making rounded corners or other rounded cuts.
This is my end result for this weeks assignment.
![alt text](image-40.jpg)
## Sources
* [Datasheet LM4871M](https://www.ti.com/lit/ds/symlink/lm4871.pdf?HQS=dis-dk-null-digikeymode-dsf-pf-null-wwe&ts=1741005529535&ref_url=https%253A%252F%252Fwww.ti.com%252Fgeneral%252Fdocs%252Fsuppproductinfo.tsp%253FdistId%253D10%2526gotoUrl%253Dhttps%253A%252F%252Fwww.ti.com%252Flit%252Fgpn%252Flm4871)
* [Arduino speaker](https://www.build-electronic-circuits.com/arduino-speaker/)
* [Arduino speaker](https://www.build-electronic-circuits.com/arduino-speaker/)

Binary file not shown.

After

Width:  |  Height:  |  Size: 76 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 296 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 455 KiB

View File

@@ -61,7 +61,69 @@ I've also made a render of the drone to visualize it for other people. Making th
## Feedback from Bas and Henk
I've gotten some feedback on my design and about the use of screens. Maybe I should only use speakers or use LED matrixes. After thinking about it I think im going to give LED matrixes a spin.
## CAM and machines
## Drone electronics
For the drone I will need a lot of electronics. But I will also need a pcb for inside the drone so I don't have any loose connections. The main board needs a couple of components. Something to step down the voltage from the big battery or I will use two separate batteries one for the motors one for the control board. I will also need a sensor to know the position of the drone and a microcontroller. I also need a lot of power to power the screens so that will also be something interesting.
### Components
* MCU
* BNO085
* Something to drive the LED matrixes
* SD card/ secondary MCU to control the matrixes
* LED (mandatory)
### Drone remote electronics
I'm also building the remote for the drone
* Potslider for the throttle
* Joystick for left-right-forward-backwards
* battery
* screen to see status of drone
* LED (mandatory)
#### Joystick
I really wanna use a joystick for this project because having 2 potmeters under each other looks a bit weird.
### KiCad
The first thing I did was import the design rules for our milling machine. I used the file from the lecture to import it from because there we set everything up together.
![alt text](image.jpg)
Now im going to grab all the components needed for the board
* [Joystick](https://www.digikey.nl/nl/products/detail/c-k/THB001P/11687191) x2
* LED
* small oled screen
* xiao espS3
I was struggling a lot when thinking on how to connect the joysticks because the data sheet says it needs 5 volts. Until I realized they where potentiometers and they should work with any voltage. So I could directly connect the Joysticks to the MCU
Instead of it looking like this.
![alt text](image-1.jpg)
This configuration wouldn't have worked anyway because the voltage regulator forces the voltage to 3.3 so the mcu will only read one value.
It now looks like this:
![alt text](image-2.jpg)
So I have 2 joysticks that are directly connected to the mcu. A screen that works on the I2C protocol and a LED.
First when routing the joysticks I realised that the Xiao has analog on both sides of the board. So if I change the schematic so it connects to the other side I have a lot less longer traces.
![alt text](image-3.jpg)
![alt text](image-4.jpg)
So like this instead of needing them to go across the entire mcu.
I forgot to apply the design rules so I imported them again and now I have to retrace everything. Thanks Irja for checking them together.
![alt text](image-5.jpg)
Then I needed to draw the outlines. To draw curved lines I used [this tutorial](https://www.youtube.com/watch?v=U0FIG2J6Zls). It's hard to get the get everything symmetrical. Maybe there is already a tool to do that but I don't know where to find it.
![alt text](image-7.jpg)
This is the result of the board.
![alt text](image-6.jpg)
## BOM (bill of materials)

Binary file not shown.

After

Width:  |  Height:  |  Size: 158 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 120 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 132 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 162 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 524 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 160 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 194 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 128 KiB