F17: Viserion

Grading Criteria

• How well is Software & Hardware Design described?
• How well can this report be used to reproduce this project?
• Code Quality
• Overall Report Quality:
  • Software Block Diagrams
  • Hardware Block Diagrams

    Schematic Quality

  • Quality of technical challenges and solutions adopted.

Abstract

This section should be a couple lines to describe what your project does.

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Responsibilities

• Aakash Menon

• Ajinkya Mandhre

• Aniket Dali

• Dheemanth Bangalore Vishwanatha

• Jean Madassery

• Manoj Ramesh Rao

• Miroslav Grubic

• Omkar Kale

• Pratap Kishore Desai

• Pratap Ramachandran

Schedule

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

Week#	Start Date	End Date	Task	Status
1	10/09/2017	10/15/2017	Research previous projects wiki page, gather useful information Discus about roles and study data sheet of the required parts Setup Git and slack accounts Order components	In progress
2	10/16/2017	10/22/2017	Design Hardware layout for the project Start Schematic Design in Eagle. Design High level software architecture. Design data flow diagram for software exchanges. Work on DBC file for CAN exchanges. Start writing software modules as per TDD approach.
3	10/23/2017	29/10/2017	Forward TDD modules to QA for further testing. Start interfacing respective components to respective Nodes and do a superficial testing of components. Finish design, prepare Gerber files and order PCB.
4	10/30/2017	11/05/2017	Fix the bugs on reverted modules. Stress test front sensors in different environment conditions (indoor, outdoor, cloudy, sunny..) and collect data with untested code. to check the interfaces, power requirements and conditioning required.
5	11/06/2017	11/12/2017	Stress test back sensor in different environment conditions (indoor, outdoor, cloudy, sunny..) Start working on sensor mount. (probably prepare design and possibly finish 3D printing) Finish Bearing Angle Calculation Interface back sensor to Sensor Node and test if controller receives data Decide about sensors mount for final design of a car. 3D or some other hardware solution. Finish Compass & GPS calibration
6	11/13/2017	11/19/2017	All sensors should be working fine by now Integrate sensor node with Master and confirm Master is receiving proper values Geographical Node should have both GPS and Compass interfaced and working together by now and sending values to Node
7	11/20/2017	11/26/2017	Mount sensors on car and start working on positioning them properly for maximum coverage Interface Geographical Node to the Master and confirm Master is receiving proper values from it
8	11/27/2017	12/03/2017	Sensors should be mounted, working and tested by now. Work on fine tuning and final SW touch
9	12/04/2017
10	12/11/2017

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Design

Discuss your hardware design here. Show detailed schematics, and the interface here.

Hardware Interface

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

Software Design

Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

Implementation

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

<Bug/issue name>

Discuss the issue and resolution.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

• Viserion Team GitLab Source Code

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.