Difference between revisions of "F17: Viserion"
Proj user7 (talk | contribs) (→Schedule) |
Proj user7 (talk | contribs) (→Schedule) |
||
| Line 62: | Line 62: | ||
*<font color="orange"> Research what kind of sensors previous projects used (ultrasonic, lidar..) Go through data sheets and decide what to use.</font> | *<font color="orange"> Research what kind of sensors previous projects used (ultrasonic, lidar..) Go through data sheets and decide what to use.</font> | ||
*Order components | *Order components | ||
| − | | | + | | Done |
| − | |||
|- | |- | ||
! scope="row" | 2 | ! scope="row" | 2 | ||
| Line 77: | Line 76: | ||
*<font color="orange"> Interface one sonic sensor to the sensor controller. Receive data and calculate distance. Write send, receive and MIA functions to be able to perform basic CAN communication.</font> | *<font color="orange"> Interface one sonic sensor to the sensor controller. Receive data and calculate distance. Write send, receive and MIA functions to be able to perform basic CAN communication.</font> | ||
*Study Android application software and approaches from previous projects. | *Study Android application software and approaches from previous projects. | ||
| − | | | + | | Done |
|- | |- | ||
| Line 90: | Line 89: | ||
*<font color="orange"> Interface all three front sonic sensor to the sensor controller. Apply filtering to get reliable data and send data to Master Controller. </font> | *<font color="orange"> Interface all three front sonic sensor to the sensor controller. Apply filtering to get reliable data and send data to Master Controller. </font> | ||
*Document Android approaches and decide on how to design the app and fix the protocol to exchange data with Bluetooth module. | *Document Android approaches and decide on how to design the app and fix the protocol to exchange data with Bluetooth module. | ||
| − | | | + | | Done |
|- | |- | ||
| Line 99: | Line 98: | ||
*Develop software modules with TDD approach. | *Develop software modules with TDD approach. | ||
*Verify interfaces, power requirements and conditioning required. | *Verify interfaces, power requirements and conditioning required. | ||
| − | *<font color="orange"> Stress test front sensors in different environment conditions indoor, outdoor and compare data. | + | *<font color="orange"> Stress test front sensors in different environment conditions indoor, outdoor and compare data. Also change different angles for sensors and find best angles for most reliable data and maximum coverage. </font> |
*Start development of GPS and Compass modules and document the efforts and ways to test the algorithm. | *Start development of GPS and Compass modules and document the efforts and ways to test the algorithm. | ||
| | | | ||
| Line 112: | Line 111: | ||
*Finish Bearing Angle Calculation. | *Finish Bearing Angle Calculation. | ||
*Mount the parts on PCB. | *Mount the parts on PCB. | ||
| − | *<font color="orange"> | + | *<font color="orange"> Interface back sensor, receive, filter and send data. All sensors should be working properly by now and master should be getting stable values even while car is on the move.</font> |
*Finish development of algorithm for Compass & GPS calibration and perform testing. | *Finish development of algorithm for Compass & GPS calibration and perform testing. | ||
| + | | | ||
| + | |||
|- | |- | ||
! scope="row" | 6 | ! scope="row" | 6 | ||
| Line 121: | Line 122: | ||
*Fix the bugs on reverted modules and pass it on to QA to re-verify. | *Fix the bugs on reverted modules and pass it on to QA to re-verify. | ||
*Integrate hardware/ verified software modules. | *Integrate hardware/ verified software modules. | ||
| + | *<font color="orange"> Prepare design and possibly try to finish 3D printing or figure out some other hardware solution for sensor mount for final car design. </font> | ||
*Verify the connections and working of mounted components. | *Verify the connections and working of mounted components. | ||
| | | | ||
| Line 131: | Line 133: | ||
*Connect individual module with master on the physical CAN bus and test the exchanges. | *Connect individual module with master on the physical CAN bus and test the exchanges. | ||
*Fix the bugs. | *Fix the bugs. | ||
| − | |||
*Verify the accuracy obtained from GPS and compass module with expected accuracy, fix bugs if required. | *Verify the accuracy obtained from GPS and compass module with expected accuracy, fix bugs if required. | ||
| + | *<font color="orange"> Mount sensors on new/final hardware solution, position them properly and test again received data while car is in move. </font> | ||
*Test Android Application with dummy data if nodes are not ready. | *Test Android Application with dummy data if nodes are not ready. | ||
| | | | ||
| Line 143: | Line 145: | ||
*Sensors should be mounted, working and tested by now. Work on fine tuning and final SW touch. | *Sensors should be mounted, working and tested by now. Work on fine tuning and final SW touch. | ||
*Integrate multiple nodes over CAN and perform integration and system testing. | *Integrate multiple nodes over CAN and perform integration and system testing. | ||
| + | *<font color="orange"> If solution for filtering sensor data is not finalized and made perfect by now, finish it immediately. </font> | ||
*Fix bugs, if any. | *Fix bugs, if any. | ||
| | | | ||
| Line 154: | Line 157: | ||
*Analyze, document the bugs, cross verify the bug. | *Analyze, document the bugs, cross verify the bug. | ||
*Fix the bugs in individual or integrated software/hardware. | *Fix the bugs in individual or integrated software/hardware. | ||
| + | *<font color="orange"> Interface Head lights and turn them ON based on light sensor value. </font> | ||
*Perform integration or unit testing to verify that bug is fixed. | *Perform integration or unit testing to verify that bug is fixed. | ||
| | | | ||
Revision as of 07:20, 30 October 2017
Contents
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.
Viserion Team RC Car
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
- 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.
Legend: Motor & I/O Controller , Master Controller , Communication Bridge Controller, Geographical Controller, Sensor Controller , Team Goal
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 | 10/09/2017 | 10/15/2017 |
|
Done |
| 2 | 10/16/2017 | 10/22/2017 |
|
Done |
| 3 | 10/23/2017 | 29/10/2017 |
|
Done |
| 4 | 10/30/2017 | 11/05/2017 |
|
|
| 5 | 11/06/2017 | 11/12/2017 |
|
|
| 6 | 11/13/2017 | 11/19/2017 |
|
|
| 7 | 11/20/2017 | 11/25/2017 |
|
|
| 8 | 11/26/2017 | 12/01/2017 |
|
|
| 9 | 12/03/2017 | 12/08/2017 |
|
|
| 10 | 12/10/2017 | 12/12/2017 |
|
|
| 11 | 12/13/2017 | 12/16/2017 |
|
|
| 12 | 12/17/2017 | 12/19/2017 |
|
|
| 13 | 12/20/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
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.
