Commit 26715097 authored by Jonathan Chery's avatar Jonathan Chery 💬
Browse files

Working on week 07

parent d751fefb
Pipeline #232709 passed with stage
in 48 seconds
# 7. Electronics design
# 7. Electronics Design
This week I worked on:
- Learning about Electronics
- Learning about EAGLE
- Learning to use EAGLE for PCB Design
# Learning about Electronics
Being new to electronics made this week difficult to naviagte. I needed to grow my understanding of electronics. To do so, I researched videos on LinkedInLearning that might provide some insight on electronics development. I found a series of vides that help build my foundation to electronics.
- Learning Electronics
- Learning EAGLE
- Redraw an echo hello-world board
- Adding Components
- Reflection
- Testing the board
## Learning Electronics
This week I spend the time growing my understanding of electronics. I researched some videos on LinkedInLearning and found several electronic foundation videos:
Some of the videos I found were:
1. [Electronics Foundations: Fundamentals by Barron Stone](https://www.linkedin.com/learning/electronics-foundations-fundamentals/welcome?contextUrn=urn%3Ali%3AlearningCollection%3A6773456169471131648&u=74653650)
2. [Electronics Foundations: Building Circuits](https://www.linkedin.com/learning/electronics-foundations-basic-circuits/build-circuits-on-breadboards?contextUrn=urn%3Ali%3AlearningCollection%3A6773456169471131648&u=74653650)
## Electronics Foundations: Fundamentals by Barron Stone
This series was helpful in understanding how electricity works. In this course, I learned about electricity and how it works. The main take away I got from this course is that, at the end of the day, when working with electronics, I'm just moving a bunch of electrons around using voltages to push them and circuits components to lead them where they need to be. This course was estimated to be 1 hour and 17 minutes.
### Breakdown of the videos
In the *Electronics Foundations: Fundamentals by Barron Stone*, I learned about electricity and how it works. The main take away I got from this course is that, at the end of the day, when working with electronics, I'm just moving a bunch of electrons around using voltages to push them and circuits components to lead them where they need to be. This course was estimated to be 1 hour and 17 minutes.
In the *Electronics Foundations: Building Circuits*, I learned about designing and assembling electronic circuits. The course was meant to give me the know how's and the understanding of how circuitry works in order to work with existing ones or design my own.
## Electronics Foundations: Building Circuits
This series, I was unable to get to due to my time constraint. This series is estimated to be 4 hours and 2 minutes. My understanding of this series was for it to teach me about designing and assembling electronic circuits. It's meant to give me the know how's and the understanding of how circuitry works in order to work with existing ones or design my own.
## Learning EAGLE
EAGLE (Easily Applicable Graphical Layout Editor) is a flexible and expandable EDA schematic capture, PCB layout, autorouter and CAM program. To download and install EAGLE, I went to [AutoDesk](https://www.autodesk.com/products/eagle/free-download?plc=F360&term=1-YEAR&support=ADVANCED&quantity=1). The installation was quite simple and sooner or later, I was up and running with the application.
# Learning about EAGLE
On top of needing to grow my understanding of electronics, I needed to learn about EAGLE. I found a LinkedInLearning video that provided a crash course on PCB Design with EAGLE. The series is called [Learning PCB Design with EAGLE](https://www.linkedin.com/learning/learning-pcb-design-with-eagle/download-your-libraries?contextUrn=urn%3Ali%3AlearningCollection%3A6773456169471131648&u=74653650) with Taylor Hokanson. This series is approximately 1 hour and 15 minutes. Unfortunately, I was unable to do this series because of my time constraint. However, I followed the FabLab tutorial on [Week 6: Electronics Design](https://fabacademy.org/2019/docs/FabAcademy-Tutorials/week06_electronic_design/eagle_english.html#download-and-install-eagle) and received help from [Greg Buckland](http://fab.academany.org/2018/labs/fablabdassault/students/greg-buckland/about.html). Both help has given me the opportunity to quickly get started with PCB Design in EAGLE. With Greg, my session often do tutorials and I used this -> [tutorial](https://www.youtube.com/watch?v=iRcj_SoxHLU) <- for guidance on this week assignment.
To learn EAGLE, I followed a LinkedInLearning course about PCB Design with EAGLE. The course was called [Learning PCB Design with EAGLE](https://www.linkedin.com/learning/learning-pcb-design-with-eagle/download-your-libraries?contextUrn=urn%3Ali%3AlearningCollection%3A6773456169471131648&u=74653650) with Taylor Hokanson. This course is approximately 1 hour and 15 minutes.
## What is EAGLE?
EAGLE (Easily Applicable Graphical Layout Editor) is a flexible and expandable EDA schematic capture, PCB layout, autorouter and CAM program.
Additionally, I followed the FabLab tutorial on [Week 6: Electronics Design](https://fabacademy.org/2019/docs/FabAcademy-Tutorials/week06_electronic_design/eagle_english.html#download-and-install-eagle) and received help from my instructor [Greg Buckland](http://fab.academany.org/2018/labs/fablabdassault/students/greg-buckland/about.html). Both resource provided me the opportunity to quickly get started with PCB Design in EAGLE. It is also worth noting that Greg, my instructor, often does tutorial session and I used a previous [tutorial](https://www.youtube.com/watch?v=iRcj_SoxHLU) for guidance on this week assignment.
## My Experience with EAGLE
To download and install EAGLE, I went to [AutoDesk](https://www.autodesk.com/products/eagle/free-download?plc=F360&term=1-YEAR&support=ADVANCED&quantity=1). The installation was quite simple and sooner or later, I was up and running with the application.
## Redraw an echo hello-world board
To start on the assignment, I opened the EAGLE application.
![eagle_application](../images/week07/eagle_application.png)
To build my comfortable of the environment and PCB Design, I used the same examples and materials shared on the Fab lab's Week 6: Electronics Design page. With that said, I build off of the [Hello Echo](https://fabacademy.org/2019/docs/FabAcademy-Tutorials/week06_electronic_design/eagle_english/hello-ftdi-44.sch) example.
My PCB design consisted of using the same examples and materials shared on the Fab lab's Week 6: Electronics Design page. With that said, I build off of the [Hello Echo](https://fabacademy.org/2019/docs/FabAcademy-Tutorials/week06_electronic_design/eagle_english/hello-ftdi-44.sch) example.
Once I opened the page, I saved the page onto my Desktop by doing "Save As" and leaving the extension to **.sch**
......@@ -49,18 +54,17 @@ Once I created the new "Schematic," I opened the [Hello Echo](https://fabacademy
![open](../images/week07/open.png)
### What is a Schematic?
In electronics, a schematic is a drawing that represents a circuit by using symbols to represent real-world electronic components. The most basic symbol is a conductor (traces) which is illustrated as a line. If wires connect in a diagram, they are shown with a dot at the intersection.
It is worth noting that a schematic, in electronics, is a drawing that represents a circuit by using symbols to represent real-world electronic components. The most basic symbol is a conductor (traces) which is illustrated as a line. If wires connect in a diagram, they are shown with a dot at the intersection.
![Schematic](../images/week07/Schematic.png)
### Important Things To Know:
It is also worth noting that:
1. Current => Flow of charge through a conductor
2. Voltage => Force that generate the Current
3. Resistance => The opposition to Current that is provided by a material, component, or circuit.
### Adding the Fab Lab Library:
To help me navigate Eagle's libraries, I decided to use the Fab Lab library that can be obtained from this link: [FabLab Library](https://github.com/Academany/FabAcademany-Resources/blob/master/files/fab.lbr)
The next step was to add the Fab Lab library to EAGLE's libraries. The Fablab library can be obtained with this link, [FabLab Library](https://github.com/Academany/FabAcademany-Resources/blob/master/files/fab.lbr)
The Fab Lab Library will ensure that I do not get lost in the Eagle's library. To download the Fab Lab library, I selected "Raw" and took me to a new page with all the raw code. From there, I right-click to "Save As" (Saved as default file - .lbr).
......@@ -68,33 +72,34 @@ Once the file was saved, I went back to Eagle and selected File > Open > Library
![library](../images/week07/library.png)
Now, I have all the Fab Lab components available to me.
![fablab_components](../images/week07/fablab_components.png)
Eagle has two windows that you use simultaneously to design a board:
1. Schematic (.sch) - logical components
2. Board Layout (.brd) for the actual board that we mill
There are 2 ways to interact with Eagle.
There are 2 ways to interact with Eagle:
1. Graphical Icons Toolbar: You can use the icons in the left-hand toolbar, mouse over them to see what they do. (enabled by default).
![graphical](../images/week07/graphical.png)
2. Command Line: You can start typing a command at any point, then select the item in the schematic / board that you wish to interact with, see section on commands below.
** If you are interested in using the Command Line, here's a list of the EAGLE commands: [Commands](http://web.mit.edu/xavid/arch/i386_rhel4/help/24.htm) **
Being new to EAGLE, I decided to use the Graphical Icons Toolbar
## Learning to use EAGLE for PCB Design
In the Hello Board, below are the parts that were already on the board:
1. 6-pin programming header: for programming the board
2. microcontroller: attiny44A. Once the microcontroller is programmed, the program stored in non-volatile memory. This means that it will remember the program.
3. FTDI header: powers the board and allows board to talk to computer
4. 20MHz resonator: external clock. The attiny has a 8Mhz clock but the resonator is faster (increase the clock speed of the processor) and more accurate.
I will be adding the following:
1. Resistor
2. Button
3. Ground
......@@ -103,8 +108,7 @@ I will be adding the following:
6. LED (Light Emitting Diode)
7. Resistor (value 499 ohms) Purpose: current limiting resistor
### Side Note:
*It was suggested that I switch out the ATTiny44 for the ATTiny412. The ATTiny412 is more relevant and has a better support for components. That said, I replaced the ATTiny 44 schmatic with the [Attiny412](https://www.microchip.com/wwwproducts/en/ATTINY412)*
*Side note, it was suggested that I switch out the ATTiny44 for the ATTiny412. The ATTiny412 is more relevant and has a better support for components. That said, I replaced the ATTiny 44 schmatic with the [Attiny412](https://www.microchip.com/wwwproducts/en/ATTINY412)*
*![attiny412](../images/week07/attiny412.png)*
......@@ -120,7 +124,7 @@ This opened a panel where I had the ability to remove Libraries. I removed the L
So, now, I need to remove the Attiny44 with the Attiny412 and reconnect the connections to the components, the VCC, and the Ground (GND).
### Adding Components
## Adding Components
To add a component, select "Add Part" from the Toolbar to the left of the application.
![add](../images/week07/add.png)
......@@ -176,8 +180,6 @@ This allowed me to connect **CAPACITOR** to ground without having to have the **
![capacitor_gnd](../images/week07/capacitor_gnd.png)
![everything_else_gnd](../images/week07/everything_else_gnd.png)
Now, becane I named the **Net** GND, where the **Net** is named GND means that those **Net** are connected electrically.
#### Connecting Power (VCC/VDD):
......@@ -218,8 +220,7 @@ For the Button, I connected it to the PA6
Final result:
![final_sch](../images/week07/final_sch.png)
## Switching to Board View
Now, I'm switching to BRD view by selecting:
Now, the next step is switching to BRD view by selecting:
![board_view_button](../images/week07/board_view.png)
......@@ -261,7 +262,6 @@ To fix it, select **Rip-up**:
I ripped up one clearance and the DRC resulted in:
![fix_clearance](../images/week07/fix_clearance.png)
## Exporting a board design
To prep my board for milling, I went to the **Layer Setting** tool to remove the unnecessary items.
![layer_setting](../images/week07/layer_setting.png)
......@@ -313,8 +313,8 @@ To prepare my PCB for milling, I used [Gimp](https://www.gimp.org/downloads/).
7. After doing the above steps, I select **File** > **Export As**
## Made Some Edits:
I realized that my PCB needed work. That said, I was able to schedule some time with [Greg](https://www.linkedin.com/in/greg-buckland-b961401a0/) and we was able to help me redesign my PCB. With his help, I was able to create a new design.
## Reflection:
I realized that my PCB needed work. That said, I was able to schedule some time with Greg and we was able to help me redesign my PCB. With his help, I was able to create a new design.
Before Greg Help:
![Trace](../images/week07/trace.png)
......@@ -327,10 +327,29 @@ After Greg Help:
From there, I went to the lab to print out my PCB:
![print_out](../images/week07/print_out.png)
# Reflection
After finishing my electron design, I was able to get some feedback on my design. In te feedback, it was identified that the 1/64 mmill was towrds the end of its functionality. This was identified due to the **Traces** that came out. I was not confident in the process and decided to redeign the cut and and cut it out. The redeign and the cut of the PCB design can be found in the [Week09](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week09/).
After finishing my electron design, I was able to get some feedback on my design. In the feedback, it was identified that the 1/64 mmill was towrds the end of its functionality. This was identified due to the **Traces** that came out. I was not confident in the process and decided to redeign the cut and and cut it out. The redeign and the cut of the PCB design can be found in the [Week09](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week09/).
![pcb_board](../images/week09/pcb_board.png)
## Testing the board
I tested the board by verifying that, when clicking the button, the LED lights up. In order to perform the test, I needed to load some code onto the board.
To get the programming working, I needed a ![UPDI 3 adapter](http://academy.cba.mit.edu/classes/embedded_programming/UPDI/hello.serial-UPDI.3.jpg). This adapter was inspired the ![schematic](http://academy.cba.mit.edu/classes/embedded_programming/UPDI/hello.serial-UPDI.3.png) using the following ![traces](http://academy.cba.mit.edu/classes/embedded_programming/UPDI/hello.serial-UPDI.3.traces.png) and ![interior](http://academy.cba.mit.edu/classes/embedded_programming/UPDI/hello.serial-UPDI.3.interior.png).
![serial_UPDI_3](../images/week09/serial_UPDI_3.png)
Once I created the adapter, I downloaded the [Arduino IDE](https://www.arduino.cc/en/software) to begin programming.
![arduino_ide](../images/week09/arduino_ide.png)
To program my board, I needed to first understand how the UPDI adapter, my PCB board, and the FTDI adapter works. I reached out to one of my instructor, [Greg Buckland](http://fab.academany.org/2018/labs/fablabdassault/students/greg-buckland/about.html), where he explained the process of embedded programming.
Once I gained an understanding of the process, I was able to test the board by writing a small amount of code that would get the LEF to light up. The results can be shown below:
![no_LED](../images/week09/no_LED.png)
![LED_working](../images/week09/LED_working.png)
......
......@@ -6,7 +6,7 @@
4. [Computer-Controlled Cutting](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week04/)
5. [Electronics Production](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week05/)
6. [3D Scanning and Printing ](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week06/)
7. [In Progress](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week07/)
7. [Electronics Design](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week07/)
8. [In Progress](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week08/)
9. [In Progress](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week09/)
10. [In Progress](http://fabacademy.org/2021/labs/dassault/students/jonathan-chery/assignments/week10/)
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment