Customer Handoff & Final Project Documentation
Table of Contents
Team Vision for Final Demo and Handoff
- Software to working state
- Assembly and Process Instruction
- Drone testing
- Resolution/frame rate requirement
Drone FailureDuring one of the recent test flights the drone accelerated unexpectedly and flew in to some branches and fell about 5 meters. The pilot noted that he felt that the drone was not responding to their inputs. The drone was recovered and a thorough damage assessment was performed.
- 5 Broken propellers
- Both landing legs bent and sheared at their base
- 1 Broken motor arm
- Shattered payload
- Incorrect Flight Mode: The drone's flight mode was incorrectly set to "Manual Mode" instead of "Position Mode" which had been used for all other testing. That meant that the pilot's control scheme was not mapped as they expected, resulting in the unexpected behavior the pilot experienced.
- Over Usage of Switch: The "Position Mode" flight mode and "Manual Mode" flight mode were assigned to the same 3 position switch, making it simple to accidentally place the vehicle in the wrong flight mode. At a distance the two flight modes can be hard to differentiate at a distance for a novice.
- Plan for Confusion: Design your control scheme to avoid control confusion and simple mistakes. Don't assign easily confused flight modes like Position and Takeoff to the same switch.
- Skilled Pilot: A more skilled pilot would have been ideal, or at least one with more experience flying large drones without FPV. In the event the team did not have a suitable pilot, one should been sought out and asked for assistance.
Scheduled to be fully repaired by Friday 4/26
Final Software StatusSoftware Diagram with Functions: Software Diagram.
- Connection Between 360 Camera and Base Station over Wifi
- Live video feed piped into a VR environment that the VR headset can view
- Ability to record and store live video feed on the computer to be replayed later
- Ability to replay the stored video to rewatch and look at different perspectives
Known issues and fixes for future developers
- Video quality at a stable frame rate
- Creating an android application that can run on the camera and mimic the getLivePreview function, which outputs a stream of MJPEG, but without the restrictions of frame rates and resolutions.
- Video can buffer and cause video to freeze up,
replaying old frames
- getLivePreview shows this video buffering on the phone app as well. By creating a more stable application, like the solution above, can fix this as this camera has shown it's capability of streaming 4k 30fps.
- Looking more into depth of the cameras ability to stream as the WiFi streaming may not use MJPEG, but some other means of streaming the data.
Suggestions for future developers
- Have team members research the language/tools they're using as soon as possible.
- Avoid spending too many hours in online forums to try and find an answer. Try talking to an SME when you can't proceed.
Areas to be improved
Testing Document: Here.
- Budget is reflected as of 4/24/2019
- We have $250 dollars for repairs
PosterPDF of Poster: Poster.
Video can be seen here: https://www.youtube.com/embed/91tdgc_JuvY
- Explain subsystems at high level
- Display example of 360 video
- Discuss areas of future improvement
- Show successes of project
- Does not discuss shortcomings
Full paper: Here.
- Improvements for the Future
- Modified API
- Makes use of the 320 Mbps transmit speed
- Improved Transmission Hardware
- Increase capability from 2k max to 4k
- Transmission through obstructions
- Modified API
- Improved Flight Time
- Reduce weight of drone
- Increase battery strength
- Improved Flight Time
- Big Ticket
- Initial Drone Purchase
- Unexpected Purchases
- Drone Fixes (legs, arms, props)
- Extra cabling
- Big Ticket
Risk / Problem Tracking
- Flying with the VR headset on
- Lack of sensors on the drone
- Use of incorrect flight modes
Team Self-AssessmentEach score is graded on a scale of 1-5 by all team members. The scale is exponential such that 1=unacceptable, 2=70% (under-performing), 3=90% (expected), 4 = 95% (exceeding expectation), 5 = 100% (well above and beyond)
- Delivered functional proof-of-concept
- Strong performance given a tight budget and small team
- Improvement in team communication
- Good starting point to be improved upon
- Missed deadlines on software resulting in under-developed feature set
- Missed deadlines on drone build causing flight testing to be delayed
- Failed to purchase the original DJI drone system so a new one had to be developed from scratch, causing a massive increase in scope
- Did not get a full hover time test
- Did not record a 2K video stream during testing
- Bugs in software can cause excessive delays and stuttering
Reflection: Lessons Learned
- Do not rely on similar experiences, issues that occurred were unique to what we were using
- Use subject matter experts early to avoid wasting
excessive time trying to solve a problem
- On that topic, check things with Gary often, and update him regularly
- Allot more time for tasks to account for unknown issues
- Have backups of critical parts
- Raise concerns early to help mitigate risks
- Communicate team action items and progress regularly
Plans for Wrap-up
- Repair drone
- Finalize edge site
- Deliver final product