Bio week 2, superpower, fabrication week 2

This commit is contained in:
Aidan Sharpe 2025-02-04 10:47:05 -05:00
parent e112227e1d
commit 4099fad339
28 changed files with 176 additions and 11 deletions

View File

@ -1,14 +1,25 @@
# What's Your Superpower - Aidan Sharpe ---
title: What's Your Superpower
author: Aidan Sharpe
date: February 3rd, 2025
geometry: margin=1in
---
## Electrical Engineering ## Electrical Engineering
| Skill | Proficiency | Experience | Potential Clients | Common |
| Skill | Proficiency | | Potential Clients | |--------------|-------------|----------------------|---------------------|--------|
|--------------------------------|-------------|---|-------------------| | PCB Design | 4/5 | Internship, clinic project, classwork | Clinics designing a PCB | 1/10 |
| PCB Design | 7/10 | | | | Electronic Component Selection | 4/5 | Internship, clinic project | Clinics designing a PCB | 1/10 |
| Electronic Component Selection | | | | | Electronic Design Review | 4/5 | Clinic project | Clinics designing a PCB | 1/10 |
| | | | |
| | | | |
## Software Development ## Software Development
| Skill | Proficiency | Experience | Potential Clients | Common |
|------------|-------------|----------------|------------------------------|--------|
| Python Programming | 5/5 | Clinic project, classwork | Lab Assistant for DSP or ECOMMS | 2/10 |
| C Programming | 4/5 | Clinic project, classwork | Lab Assistant for Embedded Systems. Clinics designing an embedded system. | 1/10 |
## Interpersonal Skills ## Interpersonal Skills
| Skill | Proficiency | Experience | Potential Clients | Common |
|-----------------|-------------|-----------------|-------------------|--------|
| Teaching | 4/5 | IEEE workshops, sailing coach, clinic project | Lab assistant | 4/10 |
| Team Management | 4/5 | Sailing coach, clinic project | | 4/10 |

View File

@ -3,7 +3,7 @@ import matplotlib.pyplot as plt
def main(): def main():
f_s = 6 f_s = 48
T_s = 1/f_s T_s = 1/f_s
t = np.arange(-1, 1, T_s) t = np.arange(-1, 1, T_s)
@ -14,7 +14,5 @@ def main():
plt.stem(t, signal) plt.stem(t, signal)
plt.show() plt.show()
if __name__ == "__main__": if __name__ == "__main__":
main() main()

View File

@ -0,0 +1,13 @@
# Clinic Consultant Notes
## Week 1
- Find a way to interact before introductions
- Mock behavioral interview
- Identify a client who has a specific **engineering design problem** that can be addressed with your expertise and skills.
- Fill out project approval form on canvas
### List of Skills
- Electronics Design: impedance control, multi-layer board design
- Programming: Python, C#, C, C++
- CAD: FreeCAD, KiCAD, Altium Designer
- IT: Linux, Windows, Docker

View File

@ -0,0 +1,30 @@
# ECE09402 Project 1A - Aidan Sharpe
## Project Overview
This project introduces basic breadboarding concepts including the orientations of power rails and terminal strips and the best practices of component layout. Through this project, we also practiced reading resistor codes, reading schematics, and correctly orienting LEDs, which are polarized devices.
We were provided with the schematic below.
![](schematic.jpg)
\newpage
All switches in "off" position; no LEDs on. This angle makes seeing the wiring layout easier.
![](wiring.jpg){width=50%}
Switch 1 in "on" position; red LED on. This angle makes seeing the state of the switches easier.
![](red_on.jpg){width=50%}
Switches 1 and 2 in "on" position; red and yellow LEDs on.
![](red_yellow.jpg){width=50%}
\newpage
Switches 1, 2, and 3 in "on" position; red, yellow, and green LEDs on.
![](red_yellow_green.jpg){width=50%}
## Key Takeaways
I was successfully able to complete all the goals set forth in the project overview. Through this exercise, I also learned that bending the pins outward on the DIP switch makes it stay in better. Additionally, I found that although the wires in the kits are pre-cut to helpful sizes, there is only one color for each size. In the future, for organizational purposes, I plan to cut wire from the spools in the back of the labs to keep consistent color for the same path or sub-circuit.

Binary file not shown.

After

Width:  |  Height:  |  Size: 538 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 357 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 426 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 236 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 141 KiB

View File

@ -0,0 +1,7 @@
@online{MorePCB,
title = {A Comprehensive Guide to Prototype Board},
author = {MorePCB},
year = 2023,
url = {https://morepcb.com/a-comprehensive-guide-to-prototype-board/},
urldate = {2025-02-03}
}

Binary file not shown.

After

Width:  |  Height:  |  Size: 255 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

View File

@ -0,0 +1,47 @@
---
title: Project 1B - Traffic Light Protoboard
subtitle: Rapid Prototyping & Fabrication
author: Aidan Sharpe (916373346)
author:
- Aidan Sharpe (916373346)
- Michelle Frolio
- Karl Dyer
date: February 3rd, 2025
geometry: margin=1in
bibliography: citations.bib
output:
pdf_document:
md_extension: native_numbering
---
\newpage
## Introduction
This exercise transitions the breadboarded circuit from the last exercise to a protoboard. We were provided with a kit of parts, which included three 220$\Omega$ axial resistors, a through-hole six-position 100-mil-pitch 90$^\circ$ pin header, and three through-hole LEDs (red, yellow, and green). Finally, we were provided with the following schematic:
![](protoboard-circuit.jpg){ width=50% }
The goal of the completed board is to have a common ground pin and individual power pins for each LEDs. This allows for independent control of the LEDs. The components are all to be permanently affixed to the protoboard with solder. In doing so, our prototype will be more durable than a simple breadboard layout.
## Procedure
First, we had to modify the protoboard and the pin header for them to mate properly. Since we are using stripboard as opposed to perfboard [@MorePCB], some of the pins would be shorted together through the pre-existing traces. We also had to remove two pins from the pin header, because the pins do not have a corresponding hole on the board.
Next, we attached the LEDs, with red on top, followed by yellow, and green at the bottom, closest to the pin header. This order matches traffic lights. Finally, we added the resistors and additional connections to match the circuit described by the schematic provided. The final board is seen below:
![](top.jpg){ width=50% #fig:top}
![](bottom.jpg){ width=50% }
The board also worked as desired, with each LED lighting up when power is applied to its respective pin. The fully lit board is seen below:
![](lit.jpg){ width=50% }
## Reflection
My first key takeaway from this exercise was that planning is key to laying out a protoboard. Espeially, since we used stripboard, it is easy to forget that two adjacent pins are connected or that there are no rails. Instead, we have to make the rails.
Another takeaway I had was that holding the wire being soldered down with the helping hands can melt and leave and remove the insulation. Luckily, this did not cause a short on the board we made.
We also learned that stripboard is not ideal for mounting pin headers on the short end. To connect a pin header in this way, both the board and the header had to be modified. Cutting traces with a utility knife works, but is far from perfect. It leaves an opening in the solder mask that could easily short and cause a board failure.
Finally, we learned how to best create solder points along a wire. Our ground wire (shown in black above) is a single wire with slits cut into it. First a segment of wire was cut, and one end was stripped and soldered into the board. Then, we marked the point along the wire where we wanted the first slit to start. We used wire strippers to cut the insulation, and then slid the insulation down the un-soldered end to create the opening. Using small lengths of uninsulated wire, we were able to make a connection from the slit to a pad on the board.
## References

Binary file not shown.

After

Width:  |  Height:  |  Size: 90 KiB

View File

@ -0,0 +1,59 @@
# Week 1 Lecture Notes
33 Slides
#### Definition: Weapon System
A weapon system is a collection of components (hardware or software) necessary to support the specific functionality of a weapon (or weapons).
## Detect
Detecting is a means to determine if an object is present.
#### Sensors
- Radar, IR, optics
- Passive listening devices
#### Network Information
- Data link
## Track
Regardless of how an object is detected, the combat system must revisit the object periodically to give the warfighter the best overall description of the area.
#### Willing Participants
- Is friend or foe (IFF)
- Missle communications
#### Non-Willing Participants
- Unidentified objects
- Threats
- Low-observable (stealth) objects
## Control
Control systems tell the combat system how to fight.
- Collects and aggregates available information
- Determines appropriate course of action
Observe $\to$ orient $\to$ decide $\to$ act
#### Definition: Engage
A means to neutralize the object with a specific weapon
## Types of Weapon Systems
- Anti-Air Warfare (AAW)
- Engage airborne threat
- Anti-Surface Warfare (ASuW)
- Engage threat at water surface
- Anti-Submarine Warfare (ASW)
- Engage underwater threat
## Seekers
#### Active
Transmit and receive RF
#### Semi-Active
Friend transmits signal, bounces off target, seeker receives
#### Passive
Listen only.