Skip to main content

Team Blog #1

Contact Info:

Name
Phone Number
Email
Asmaa Darwish
(408)-442-9922
asmaa98darwish@gmail.com
Justin Ghieuw
(510) 676-6681
j.ghieuw@gmail.com
Julio de Pereda Banda
(951)-587-7763
chargers1756@gmail.com
Shane Fatehi 
(408)-306-3044
shane.fatehi@gmail.com
Lissette Romero
(831)-241-3912
lizzie6879@gmail.com

Availability:

Scope of Work and Goals:
This year, the small scale teams scope of work is to:
- Develop a sustainable and efficient manufacturing process for the railway
- Design a railway that is repeatable and interchangeable
- Redesign bogie and railway (specifically at the y-junction) so that there is no risk of failure at the y-junction
- Design a bogey with the necessary sensors/electrical hardware which will allow for multiple pods to be on the railway at the same time without the risk of collision
- Possibly develop an app to be able to communicate back and forth with the bogies from users mobile device

The main goal is to build from prior years small scale designs and make the small scale model as reliable, efficient, and secure as possible. Another main goal would be to have the small scale model be able to be replicated as closely as possible to the half and full-scale model. This is something that has been lacking in the past years, however, it is a very important part of the project as a whole, especially in the long term when the full scale is actually ready to be built.

Written by: Julio de Pereda Banda





Comments

Popular posts from this blog

Team Blog #21

SSST Blog 4/15/2020 During this week's class meeting, all teams met with prof Furman to discuss the engineering ethics assignment. We had a very thoughtful discussion as a class in answering ethical questions about the Boeing 737 disaster and how engineers could have prevented it, by applying the engineering ethics. We discussed that three main engineering ethics were violated; the Fundamental canon, the Informed Consent, and the precautionary principle. We also discussed the best solution to take as an engineer if you found a problem at work that will have the potential to put people's lives in danger. After the discussion was over, we had some time as a team to discuss the progress of our work. Last week, the team presented their second presentation of the semester, and a lot of progress was done. The team went over the tasks that were a little behind and discussed how we will approach simulating our work using softwares like Solidworks. For bogie: Julio was able...

Team Blog #15

Progress for this week: Controls Team: To become more familiar with the Pixy Cam several tests were conducted throuhgout the week. After the team decided to switch over to barcodes for the stations the team saw that this method was better. A sheet of the 10 barcodes was then printed out and the team tested how accurate the pixy cam was at ientifying the different codes. The team will is now working on trying to develop a test which will incorporate the arduino along with the other electrical componenets. Figure 1: Barcode recognition by Pixy2 Guideway Team: The guideway team made progress on determining how the track will be supported and what materials we will use to build it. The team setteled on using mdf wood with a thickness of .25". The laser cutter cuts the wood accurately and precisely at the maker space, however, the space is only available during the week days from 10am to 6pm. The supporting stands will use 3ft long zinc threaded rods with nots and washers to ...

Team Blog #11

SSST Blog 10/17/19 Progress for the week: Controls Team  This week for the controls team, Asmaa continued working on combining the two main Arduino codes which we have so far. One of the codes was the one which implemented the ultrasonic sensor to get the motor to slow down if the ultrasonic sensor detected an object too close to it. This mimics what we want the bogies and pods to do once they are fully operational, it is essentially collision prevention system to where if a pod gets too close to another pod, the ultrasonic sensors will detect the proximity, and get the motor to slow down. The other Arduino code which we have is for the BLE. Using a pre mad app to test if the BLE works, Asmaa wrote a code to enable the Arduino to turn an LED on and off depending on the input of the user on the app. If we typed 1, the LED would turn on and if we typed 0, the LED would turn off. Asmaa combined both of these codes into one, with the slight difference that once we have our own iO...