RIT will permanently shut down the RIT Wiki (Confluence wiki) on February 2, 2024. Review the Wiki Shut Down Overview for information on alternative tools, exporting content from the wiki, and other FAQs.
Your website should document your journey through MSD, so include work-in-progress as well as latest results. Use pdf's for display whenever possible so that information is easily viewable without the need to download files and open applications. (Your Confluence file repository should still contain original editable files).
All template text must be removed prior to your Final Demo and Handoff
Team Vision for Final Demo and Handoff
| Name | 3-Week Plan | Tasks Accomplished | |
|---|---|---|---|
Andy Meyer | |||
| Piers Kwan | |||
Sabrina Ly | |||
| Ben Palmer | MSD2-49 This task involves assembling the motor onto the nacelle. MSD2-53 This task involves wiring and attaching wing mounted electronics. As I am wing owner I will oversee and work on this task, but this task is not mine alone, as I am not the electronics owner(s). MSD2-55 This task involves cutting the skin for the wings and affixing it in place. MSD2-56 This task involves attaching the wings to the fuselage and applying identification livery MSD2-70 This task involves filling the motor nacelles with expanding foam to dampen motor vibrations. MSD2-90 This task involves creating the poster | MSD2-49 - Incomplete The motors have instead been assembled onto motor mounts for the Versa Wing Test Bed. MSD2-53 - Incomplete Wiring and mechanical assembly was focused on the Versa Wing Test Bed instead. MSD2-55 - Incomplete This task cannot be completed until the wing electronic have been mounted, so this task was stalled for this phase. MSD2-56 - Incomplete We do not have a physical fuselage and even if we did the wing assembly has been stalled this phase. MSD2-70 - Incomplete This cannot happen until the motors are mounted; stalled by MSD2-49. MSD2-90 - Complete The poster has been created. | |
Mutahir Mustahsan | MSD2-49 This task involves assembling the motor onto the nacelle. MSD2-54, MSD-59 This task involves fully assembling the parachute system and fitting it to the Versa Wing MSD2-70 This task involves filling the motor nacelles with expanding foam to dampen motor vibrations. MSD2-90 This task involves creating the poster | MSD2-49 - Incomplete The motors have instead been assembled onto motor mounts for the Versa Wing Test Bed. MSD2-54, MSD-59 - incomplete The parachute was too big for the canister however parachute construction was complete bridal attached and test of the parachute itself was completed it was capable of its desired mission. MSD2-70 - Incomplete This cannot happen until the motors are mounted; stalled by MSD2-49. MSD2-90 - Complete The poster has been created. | |
| Atulya John | MSD 2-86 This task relates to the integrating the system. MSD 2-78 Place the order for the PCB. MSD 2-89, MSD 2-90 This task relates to writing the poster and technical paper. MSD 2-77 Test the PCB and verify that it is working as expected. | MSD 2-86 - Complete The PCB was tested and all the microcontrollers and sensors were connected to the board. The various devices are able to connect to each other. MSD 2-78 - Complete The order was placed and the PCB was received. MSD 2-89, MSD 2-90 - Complete The paper and poster has been completed. MSD 2-77 - Complete The PCB has been tested and its functionality has been verified. In addition to these tasks, the PCB designed at the end of the previous phase was revised and was made smaller to better fit the drone. |
Design Updates
Electrical
Final PCB Design
3D Rendering
TOP VIEW BOTTOM VIEW
Mechanical
3D Rendering - Final
Conceptual Wing - Final Stage Construction
Environmental Impact Benchmarking
Test Results Summary
PCB Testing
- The PCB was tested for shorts
- Voltage was applied to Vin on the board, and the functionality of the regulators were verified by measuring Vout at the appropriate pins.
- All the components were connected to the board and they are all receiving power and are able to communicate with each other.
Summarize Test results in your Requirements and Testing.xlsx doc and assess effectiveness of test plans to unambiguously demonstrate satisfaction of the engineering requirements. Include photos and videos as appropriate
Inputs & Source
- Test Plan
- Results of system integration
Outputs & Destination
- Test Results
- Final documentation: paper, poster, manuals
Risk and Problem Tracking
Resolved
Risk | Description | Risk Type | Likelihood (0-5) | Severity (0-5) | Importance (L x S) | Action(s) Plan/ Resolution |
|---|---|---|---|---|---|---|
| COVID-19 | School closes again before the end of the semester. | Safety | 0 | 5 | 15 | Pivot to documentation of existing systems. / School did not shut down pre-maturely. |
| Injury | Someone could be hit by the drone or cut by the propeller. | Safety | 0 | 5 | 10 | Designate a spotter, mark dangerous areas, have carefully designed testing plans, and test drones away from residential areas. / No one was injured during any of the testing. |
| Loss of Drone | With the current budget, only one drone can be manufactured. Losing this drone could prove fatal to the project. | Resource | 0 | 4 | 8 | Test all subsystems on the VersaWing before deploying to minimize risk. If the drone is lost, pivot to the documentation of existing systems. / Testing was all subverted to the VersaWing with a one time test expectancy. |
| Overspending | Budget is limited with no funding outside of team members and RIT. | Resource | 0 | 5 | 15 | All parts are picked out such that the budget is not violated. Ensure that modifications to the design are necessary and do not vastly violate the existing budget. / All necessary parts were purchased. |
| Motor Overheat | The motors are designed to be cooled by air passing through the motor in flight. This could potentially overheat in VTOL mode as less air is passing through the motors. | Technical | 0 | 2 | 4 | Takeoff and landing are when this risk is greatest. Because these modes are a small portion of the operation of the craft, no actions will be taken unless it becomes more severe. / Unable to implement VTOL mode. |
| Vibrations | Flight and motors will cause vibrations over the craft. | Technical | 0 | 2 | 10 | It is likely the craft will vibrate, but functionality is expected to remain unharmed. No actions will be taken unless it becomes more severe. / Unable to achieve extended flight, making vibration threat null. |
| Magnetic Fields | Motors and power circuits will generate and collapse magnetic fields that may interfere with positional sensors. | Technical | 0 | 1 | 4 | The sensor package should be placed as far away from the magnetic fields as possible. It seems that it is unlikely that these fields will cause significant errors in the sensors. / Sufficient distance was placed between the sensor packet and the motors to mitigate magnetic field effect. |
| Sensor Variance | Noise on the sensors could prove fatal to our application. | Technical | 0 | 4 | 16 | Noise characterization, filtering, and calibration will be performed on the sensor packages. / Noise from ground movement has been filtered while noise from flight is negligible as extended flight was not achieved. |
| Software Bug | Unexpected bugs could prove fatal mid flight. | Technical | 0 | 5 | 15 | Software best practices and review processes can limit the probability of fatal bugs. / Drone has not reached full flight capability so these bugs would never occur. |
| Manufacturing Access | Manufacturing tools could be busy, or available building resources could be limited. | Time | 0 | 3 | 9 | Source materials and fabricate parts as soon as possible. / All necessary manufacturing has been complete. |
| Early Winter | Inclement conditions could make flight testing difficult. | Time | 0 | 4 | 8 | Outfit the VersaWing so that computer subsystems are able to be tested. Manufacture drone as soon as possible to maximize number of flight tests. / Outdoors testing was minimal and weather did not have prove to be detrimental to the tests accomplished. |
Customer Redirection | A new customer is added, thus changing CRs | Time | 0 | 4 | 4 | At this point it is not feasible for the team to take on a new customer. / No new customer added. |
| Customer Absence | No official outside customer is identified, leaving us with speculated CRs and little expert knowledge | Information | 0 | 2 | 10 | We have been continuing our design validation and analysis techniques. / Design validation and choices were finalized. |
Loss of Team Member | Reduced work capacity due to missing/absent team members. | Resource | 0 | 1 | 5 | Mitigation plan is to reduce our dependency on custom mechanical parts. (Ben is leaving) / Ben did not leave. |
Problem Tracking
Loading
Final Project Documentation
Plans for Wrap-up
| Name | Wrap-Up Plan |
|---|---|
| Andy Meyer | Work with Sabrina and Piers to complete the Lightning talk Work with Sabrina and Piers to complete the paper with updated results Finish updating confluence with final documents |
| Piers Kwan | Work with Andy and Sabrina to complete the Lightning talk Work with Andy and Sabrina to complete the paper Finish updating confluence with final documents |
| Sabrina Ly | Work with Andy and Piers to complete the Lightning talk Work with Andy and Piers to complete the paper Finish updating confluence with final documents |
| Ben Palmer | |
| Mutahir Mustahsan | |
| Atulya John |