Commit 96d2f527 authored by Teddy Warner's avatar Teddy Warner
Browse files

Merge branch 'master' of gitlab.fabcloud.org:theodore.warner/site

parents 44880e1e b03e4d81
Pipeline #229570 passed with stage
in 37 seconds
...@@ -8,6 +8,9 @@ This week's group assignment was to review the safety data sheets of several dif ...@@ -8,6 +8,9 @@ This week's group assignment was to review the safety data sheets of several dif
<iframe src="https://drive.google.com/file/d/1IHOmytiUM8FNJdP9NZBQzmAlZ0Rx9HHU/preview" width="700" height="600"></iframe> <iframe src="https://drive.google.com/file/d/1IHOmytiUM8FNJdP9NZBQzmAlZ0Rx9HHU/preview" width="700" height="600"></iframe>
As repeatedly described throughout the data sheet, it is crucial to always practice the correct safety measures. This includes some very obvious things like not ingesting the material, but also has other important details such as performing any casting in a well ventilated area. We casted with each of the materials in the room where we have all our soldering irons and the laser cutters, so we already had a professional filtration and ventilation system in that room. Another important thing is that to remove any material that may have spilled on our hands during the mixing process, the only thing you need to use is soap and warm water. On the [Smooth Cast 300 website](https://www.smooth-on.com/products/smooth-cast-300/), there is more information about curing. Since the Smooth Cast 300 cures in about 5 minutes, the reaction is highly exothermic and can reach very high temperatures as seen at the bottom of this site.
## Molding & Casting Tests ## Molding & Casting Tests
### Milling ### Milling
......
# Networking & Communication # Networking & Communication
This week our group experimented with networking & communication through communicating between two projects, and sending and recieving a message. This week our group experimented with networking & communication through communicating between two projects, and sending and receiving a message.
We communicated between the final project boards of studnets [Drew Griggs](http://fabacademy.org/2021/labs/charlotte/students/drew-griggs/) and [Teddy Warner](http://fabacademy.org/2021/labs/charlotte/students/theodore-warner/). We communicated between the final project boards of students [Drew Griggs](http://fabacademy.org/2021/labs/charlotte/students/drew-griggs/) and [Teddy Warner](http://fabacademy.org/2021/labs/charlotte/students/theodore-warner/).
## Hardware ## Hardware
We started by hooking up our boards. Drew's final project included the use of both software and hardware serial, so we used that board as a "slave" board. We had it recieve messages through the software serial port, and send them out to a monitor through the hardware serial ports. We started by hooking up our boards. Drew's final project included the use of both software and hardware serial, so we used that board as a "slave" board. We had it receive messages through the software serial port, and send them out to a monitor through the hardware serial ports.
Teddy's board included many more pin headers for an LCD display, as well as a power regulator to drop power down from 12V, tx/rx pins, and other features. These extra features make it optimal if we wanted to hook up multiple different boards to it, so we used it as a master board. Teddy's board included many more pin headers for an LCD display, as well as a power regulator to drop power down from 12V, tx/rx pins, and other features. These extra features make it optimal if we wanted to hook up multiple different boards to it, so we used it as a master board.
![](../images/week11/serialconnections.jpg) ![](../images/week11/serialconnections.jpg){width="600px"}
We connected the programming pins to their respective locations, and programmed our boards. Drew's board uses FTDI protocol, so we hooked up an FTDI chip to program it. Teddy's board uses ISP protocol, so we connected an arduino uno programmed with "Arduino as ISP" to program it. We connected the programming pins to their respective locations, and programmed our boards. Drew's board uses FTDI protocol, so we hooked up an FTDI chip to program it. Teddy's board uses ISP protocol, so we connected an arduino uno programmed with "Arduino as ISP" to program it.
...@@ -64,7 +64,7 @@ The master code simply prints an incrementing integer every 1/2 second. ...@@ -64,7 +64,7 @@ The master code simply prints an incrementing integer every 1/2 second.
We uploaded our code using our different protocols and starting testing. We connected the tx pin of Teddy's board to the software serial rx pin on Drew's, opened the serial port, and found ourselves reading an incrementing integer We uploaded our code using our different protocols and starting testing. We connected the tx pin of Teddy's board to the software serial rx pin on Drew's, opened the serial port, and found ourselves reading an incrementing integer
![](../images/week11/runnignsystem.jpg) ![](../images/week11/runningsystem.jpg)
<iframe width="800" height="650" src="https://www.youtube.com/embed/Qtg5RR7s4lg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> <iframe width="800" height="650" src="https://www.youtube.com/embed/Qtg5RR7s4lg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
......
Markdown is supported
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