mirror of
https://gitlab.waag.org/make/fablab/interns/2025/sam.git
synced 2025-08-05 13:06:56 +00:00
Compare commits
6 Commits
a46ad186db
...
main
Author | SHA1 | Date | |
---|---|---|---|
774f7f41d6 | |||
2a585ff318 | |||
e700818a2f | |||
6be2d84f05 | |||
d943d6239e | |||
7a4b75c0a3 |
@@ -1,7 +1,7 @@
|
||||
# FR-1 Trace lengths
|
||||
|
||||
## The experiment
|
||||
For the experiment, I used FR-1 that has a thickness of 35µm. On there I will mill 4 trace sizes (0.4 mm, 0,6 mm, 0,8 mm and 1 mm) and they all have the same length of 7.5 cm’s. The traces are seperated by 1 Cm.
|
||||
For the experiment, I used FR-1 that has a thickness of 35µm. On there I will mill 4 trace sizes (0.4 mm, 0,6 mm, 0,8 mm and 1 mm) and they all have the same length of 7.5 cm’s. The traces are separated by 1 Cm.
|
||||
|
||||

|
||||
|
||||
@@ -26,26 +26,29 @@ The capacitance of a PCB trace is the amount of energy it can hold. It works lik
|
||||
The capacitance is determined by the amount of copper is in the trace. So length, width and the thickness. When working with low frequency signals the capacitance is not super important.
|
||||
But when working with higher speed frequencies the capacitance can actually mess up the signal integrity.
|
||||
|
||||
## Heat generation
|
||||
Heat within traces is generated by the current flowing through it. Not the wattage. A good example of the is train lines. These run on 230.000 volts on thin wires while being able to supply multiple trains. The higher the voltage the easier it is the transport a higher amount of wattage.
|
||||
|
||||
## Results
|
||||
|
||||
the power. So I grabbed an old robot with 4 stepper motors attached but I could not get them to draw more than 30 watts. So that is why the maximum in this test is 30 watts. I also had a hard time finding a way to measure the temperature of the traces because we only had a heat gun here and the laser was not the place it was actually measuring. So 0,4 mm is not measured properly.
|
||||
the power. So I grabbed an old robot with 4 stepper motors attached but I could not get them to draw more than 1.6 Amperage. So that is why the maximum in this test is 1.6 Amperage. I also had a hard time finding a way to measure the temperature of the traces because we only had a heat gun here and the laser was not the place it was actually measuring. So 0,4 mm is not measured properly.
|
||||
|
||||
| Trace Width Trace | Resistance | Maximum safe wattage | Burn out wattage |
|
||||
| :---------------- | ---------- | -------------------- | ---------------- |
|
||||
| 0,4mm | 3,1Ω | 15 | 20 |
|
||||
| 0,6mm 2 | 2Ω | 22 | 26 |
|
||||
| 0,8mm | 2Ω | 27 | ?? |
|
||||
| 1mm | 1,85Ω | ?? | ?? |
|
||||
| | | | |
|
||||
| Trace Width Trace | Resistance | Maximum safe Current in Ampere | Burn out Ampere |
|
||||
| :---------------- | ---------- | ------------------------------ | --------------- |
|
||||
| 0,4mm | 3.1Ω | 0.7 | 0.85 |
|
||||
| 0,6mm | 2.7Ω | 0.9 | 1.05 |
|
||||
| 0,8mm | 2Ω | 1.6 | ?? |
|
||||
| 1mm | 1.85Ω | ?? | ?? |
|
||||
| | | | |
|
||||
|
||||
|
||||
* The 0,4 mm trace was the first one I tested. I started with 15 watts for a few seconds. After that I increased the wattage to 20 watts and the trace instantly exploded and burned so I could not get temperature readings there.
|
||||
* The 0,4 mm trace was the first one I tested. I started with 0.7 amps for a few seconds. After that I increased the wattage to 0.85 amps and the trace instantly exploded and burned so I could not get temperature readings there.
|
||||
|
||||
* The 0,6 mm trace it held up well up to 27 watts where it started getting burn marks within a 5-10 seconds. The temperature rose to 50 degrees celsius. At 29 watts the pcb burned out at 68 degrees celsius.
|
||||
* The 0,6 mm trace it held up well up to 0.9 amps where it started getting burn marks within a 5-10 seconds. The temperature rose to 50 degrees celsius. At 1.05 amps the pcb burned out at 68 degrees celsius.
|
||||
|
||||
* When testing the 0,8 mm trace I hit a roof with how much power I could consume with the robot. I could only get up to 30 watts and I did not manage to break the trace after powering it for a few minutes. The maximum I found before it started discoloring was 24 watts at 54 degrees celsius. This was measured after it was left on for 2 minutes.
|
||||
* When testing the 0,8 mm trace I hit a roof with how much power I could consume with the robot. I could only get up to 1.6 amps and I did not manage to break the trace after powering it for a few minutes. The maximum I found before it started discoloring was 24 watts at 54 degrees celsius. This was measured after it was left on for 2 minutes.
|
||||
|
||||
* I could not get to the 1mm trace because the robot could not draw more than 30 watts. So thats why these are not filled in the table.
|
||||
* I could not get to the 1mm trace because the robot could not draw more than 1.6 Amperage. So thats why these are not filled in the table.
|
||||
|
||||
|
||||
## Extra notes on temperature
|
||||
|
BIN
docs/final_project/DroneMain.f3z
Normal file
BIN
docs/final_project/DroneMain.f3z
Normal file
Binary file not shown.
BIN
docs/final_project/DroneMainBody.stl
Normal file
BIN
docs/final_project/DroneMainBody.stl
Normal file
Binary file not shown.
BIN
docs/final_project/New DroneArm v5.f3d
Normal file
BIN
docs/final_project/New DroneArm v5.f3d
Normal file
Binary file not shown.
BIN
docs/final_project/SidePanel.stl
Normal file
BIN
docs/final_project/SidePanel.stl
Normal file
Binary file not shown.
BIN
docs/final_project/arm.stl
Normal file
BIN
docs/final_project/arm.stl
Normal file
Binary file not shown.
BIN
docs/final_project/drone_control_board.zip
Normal file
BIN
docs/final_project/drone_control_board.zip
Normal file
Binary file not shown.
@@ -1,29 +1,29 @@
|
||||
# Final project
|
||||
|
||||
## Introduction
|
||||
I wanted to combine 2 random objects that interest me into one project. A drone and a jumbotron. So im gonna make a drone with multiple screens on it that could for example be used for traffic control or entertainment purposes.
|
||||
I wanted to combine 2 random objects that interest me into one project. A drone and a jumbotron. So im gonna make a drone with multiple screens on it that could for example be used for traffic control or entertainment purposes. There is no real reason why I chose to make this beside it looking and sounding fun to design and build.
|
||||
|
||||
## What does the drone do?
|
||||
The drone needs to be able to fly for at least 20 minutes. It needs 2 screens on both side so it can display images or video. I wanna program the drone myself so I know how drones work and how they keep themselves upright.
|
||||
|
||||
## Drone Requirements
|
||||
### basic requirements
|
||||
* 2 screens
|
||||
* Speakers
|
||||
* 20 min flight time
|
||||
* custom microcontroller pcb that controls the drones and screens
|
||||
* 50 meter range from controller
|
||||
??? Drone Requirements
|
||||
### basic requirements
|
||||
* 2 screens
|
||||
* Speakers
|
||||
* 20 min flight time
|
||||
* custom micro controller pcb that controls the drones and screens
|
||||
* 50 meter range from controller
|
||||
|
||||
### Sensors
|
||||
* GPS
|
||||
* IMU/rotation sensor
|
||||
* Read voltage from battery know battery percentage
|
||||
### Sensors
|
||||
* GPS
|
||||
* IMU/rotation sensor
|
||||
* Read voltage from battery know battery percentage
|
||||
|
||||
### Requirements when far ahead
|
||||
* Docking station
|
||||
* Automatic docking
|
||||
* Automatic pathing
|
||||
* Design own electronic speed controllers
|
||||
### Requirements when far ahead
|
||||
* Docking station
|
||||
* Automatic docking
|
||||
* Automatic pathing
|
||||
* Design own electronic speed controllers
|
||||
|
||||
## Images
|
||||
|
||||
@@ -50,7 +50,7 @@ When designing the drone I wanted to do everything parametric. So im going to tr
|
||||
### Designing the drone parametrically
|
||||
Designing parametrically is very hard because every constraint needs to be perfect. Otherwise when changing lengths the design will fold into itself like this.
|
||||

|
||||
I've spend one day getting the constraints perfect for the sketch so it scales well with everything. And this is the result of that. When I change one parameter in the variable menu the entire body scales with it. This is the final result of my design. I've made the body myself and I've imported the components from grabcad. So I had more time for blender and Onshape and so I could visualize it better.
|
||||
I've spend one day getting the constraints perfect for the sketch so it scales well with everything. And this is the result of that. When I change one parameter in the variable menu the entire body scales with it. This is the final result of my design. I've made the body myself and I've imported the components from GrabCad. So I had more time for blender and Onshape and so I could visualize it better.
|
||||

|
||||
|
||||
### Rendering
|
||||
@@ -143,13 +143,15 @@ For the drone I will be using the [dRehmFlight VTOL program](https://github.com/
|
||||
```mermaid
|
||||
classDiagram
|
||||
namespace Drone {
|
||||
class ESPC6 Thread 1{
|
||||
class ESPC6{
|
||||
+Control Motors
|
||||
+keep drone in the air
|
||||
+Receive communication from controller
|
||||
Flightcontroller()
|
||||
}
|
||||
class MatrixControllerThread2 {
|
||||
class MatrixControllerRP2040 {
|
||||
+Receive communication from ESPC6 for Matrix data
|
||||
ShowMatrix()
|
||||
|
||||
}
|
||||
|
||||
@@ -164,13 +166,15 @@ namespace Controller {
|
||||
}
|
||||
}
|
||||
|
||||
ESPC3 --> ESPC6 Thread 1 : Send data to flight controller using ESPNOW
|
||||
ESPC3 --> ESPC6 : Send data to flight controller using ESPNOW
|
||||
ESPC6 --> MatrixControllerRP2040 : Serial communication
|
||||
|
||||
```
|
||||
Now that I am in week 15 this has changed. The change is on the drone are going to be 2 mcu's. One for the matrixes and one for the flight controller. So they are both separate systems and can't interfere with each other.
|
||||
|
||||

|
||||
|
||||
I've already gotten the motors to spin in [week 10](../Assignments/week_10_output_devices/output_devices.md) using the script in there. Now I also need to modify the original VTOL driver so my ESC's can properly understand it's instructions.
|
||||
I have already gotten the motors to spin in [week 10](../Assignments/week_10_output_devices/output_devices.md) using the script in there. Now I also need to modify the original VTOL driver so my ESC's can properly understand it's instructions.
|
||||
|
||||
There's one specific function I need to change.
|
||||
??? Old code
|
||||
@@ -344,6 +348,10 @@ Now I needed to make the same holes through the case itself in the same location
|
||||
From this tab I can edit the body with all the references in place. So I could use the holes in the drone arm as reference for my cuts for in the drone body.
|
||||

|
||||
|
||||
## 3D printing
|
||||
I chose to fully 3D print my drone due to it's complex shape and time constraints. I still had a lot of work from university to do. We got encouraged to do compositing but that is super hard with the current design. However it would have been better since it is often lighter and more durable while being a lot more eco friendly. For 3D printing I am planning on using PLA because it has a lower carbon footprint than ABS and it releases less toxic fumes.
|
||||
|
||||

|
||||
|
||||
## Burnout!
|
||||
### Part 1
|
||||
@@ -366,6 +374,7 @@ This time it was completely my fault for not paying attention to the wires when
|
||||

|
||||
|
||||
<video controls src="../PXL_20250528_093723437(1)(1).mp4" title="Title"></video>
|
||||
|
||||
## Cables
|
||||
The drone needs lots of cables to get power to the places where they need to be. I first started out by laying out everything that needed to be connected.
|
||||
|
||||
@@ -415,7 +424,7 @@ I tested the power consumption on the matrix by setting the brightness to 100 an
|
||||

|
||||
The result of this is that a single matrix consumed 3,8 amps at 5 volt. With 4 ESC's providing a total of 12 amps at 5 volts I should be easily able to power the mcu's and the matrixes.
|
||||
## Assembly
|
||||
Here I started assembly of the drone. I printed the motor arms and screwed all the motors into them and soldered pogo pins to each to connect them to the esc's. Unfortanetly I don't know how to connect them yet because the wires aren't labeled. 2 motors need to spin left and the other 2 right for stability.
|
||||
Here I started assembly of the drone. I printed the motor arms and screwed all the motors into them and soldered pogo pins to each to connect them to the esc's. Unfortunately I don't know how to connect them yet because the wires aren't labeled. 2 motors need to spin left and the other 2 right for stability.
|
||||

|
||||
I also saw during assembly that the drone body warped a bit but that isn't going to ruin the fun. It will still fly.
|
||||

|
||||
@@ -503,14 +512,14 @@ Now that the drone is ripped into several pieces I will be abandoning this desig
|
||||
| | | |
|
||||
|
||||
#### Files
|
||||
* [Drone main body F3D]
|
||||
* [Drone arm F3D]
|
||||
* [Drone main body STL]
|
||||
* [Drone main arm STL]
|
||||
* [Drone side panel STL]
|
||||
* [Drone PCB's KiCad]
|
||||
* [Drone Software]
|
||||
* [Matrix Software]
|
||||
* [Drone main body F3Z](DroneMain.f3z)
|
||||
* [Drone arm F3D]("New DroneArm v5.f3d")
|
||||
* [Drone main body STL](DroneMainBody.stl)
|
||||
* [Drone main arm STL](arm.stl)
|
||||
* [Drone side panel STL](SidePanel.stl)
|
||||
* [Drone PCB's KiCad](drone_control_board.zip)
|
||||
* [Drone Software]()
|
||||
* [Matrix Software]()
|
||||
|
||||
### Drone controller
|
||||
#### Parts
|
||||
|
BIN
docs/final_project/image343.jpg
Normal file
BIN
docs/final_project/image343.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 80 KiB |
Reference in New Issue
Block a user