Difference between revisions of "F17: Viserion"
Proj user7 (talk | contribs) (→Schedule) |
Proj user7 (talk | contribs) (→Schedule) |
||
Line 100: | Line 100: | ||
*<font color="blue"> Improve the trajectory of the car using algorithm based on speed and directions</font> | *<font color="blue"> Improve the trajectory of the car using algorithm based on speed and directions</font> | ||
*<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> | *<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> | ||
− | *<font color="CARROT">Start development of software modules for GPS and Compass modules and document the efforts and ways to test the algorithm.</font> | + | *<font color="CARROT">Start development of software modules for GPS and Compass modules and document the efforts and ways to test the algorithm.</font> |
+ | *<font color="blue"> Interface RPM sensor and measure Speed.</font> | ||
*<font color="clouds">Test can bus communication by mounting master, sensor and motor modules and transmitting master related commands.</font> | *<font color="clouds">Test can bus communication by mounting master, sensor and motor modules and transmitting master related commands.</font> | ||
− | + | *<font color="black">Mount the parts on off shelf PCB for Demo 1 and verify the wiring connections and verify that CAR is ready for the demo, </font> | |
| | | | ||
Line 110: | Line 111: | ||
| 11/12/2017 | | 11/12/2017 | ||
| | | | ||
− | |||
*<font color="orange"> Finish Bearing Angle Calculation. </font> | *<font color="orange"> Finish Bearing Angle Calculation. </font> | ||
− | *<font color="clouds"> | + | *<font color="clouds"> Control the Car's speed on detection of obstacle.</font> |
− | *<font color=" | + | *<font color="blue"> Share the RPM sensors value with master.</font> |
*<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> | *<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> | ||
*<font color="CARROT">Finish development of algorithm for Compass & GPS calibration and verify that the direction obtained from the modules with that of any off shelf smartphone's Compass.</font> | *<font color="CARROT">Finish development of algorithm for Compass & GPS calibration and verify that the direction obtained from the modules with that of any off shelf smartphone's Compass.</font> | ||
Line 127: | Line 127: | ||
*<font color="grey"> Share Gerber files with the PCB fabrication house and order 2 PCB. | *<font color="grey"> Share Gerber files with the PCB fabrication house and order 2 PCB. | ||
*<font color="purple">Design basic Android application UI, which can verify that the communication with BT module was successful or not </font> | *<font color="purple">Design basic Android application UI, which can verify that the communication with BT module was successful or not </font> | ||
+ | *<font color="black"> Car should now move without hitting "any" obstacle when powered on. Car should be able to take a reverse if required.</font> | ||
| | | | ||
Line 144: | Line 145: | ||
| 12/01/2017 | | 12/01/2017 | ||
| | | | ||
− | *<font color="black"> | + | *<font color="black"> If the link between Geo, BT, master and Motor module is working, perform outdoor system testing. </font> |
− | *<font color=" | + | *<font color="blue"> Connect battery output to ADC channel and read back the battery parameters. </font> |
+ | *<font color="orange"> Interface Head lights and turn them ON based on light sensor value. </font> | ||
| | | | ||
Line 153: | Line 155: | ||
| 12/08/2017 | | 12/08/2017 | ||
| | | | ||
− | * | + | *<font color="cloud"> Display the battery parameters on LCD. </font> |
− | * | + | *<font color="black">Perform round 1 of system testing. </font> |
− | + | *<font color="black">Start documenting project report by collaborating artifacts produced during project development. </font> | |
− | *<font color=" | + | *<font color="black">Fix the bugs in system testing. </font> |
− | * | ||
| | | | ||
Line 165: | Line 166: | ||
| 12/12/2017 | | 12/12/2017 | ||
| | | | ||
− | *Perform round 2 of system testing. | + | *<font color="black"> Perform round 2 of system testing.</font> |
− | *Start documenting project report by collaborating artifacts produced during project development. | + | *<font color="black"> Start documenting project report by collaborating artifacts produced during project development.</font> |
− | *Fix the bugs in system testing. | + | *<font color="black"> Fix the bugs in system testing.</font> |
| | | | ||
Line 175: | Line 176: | ||
| 12/16/2017 | | 12/16/2017 | ||
| | | | ||
− | *Perform round 3 of system testing. | + | *<font color="black"> Perform round 3 of system testing.</font> |
− | *Work on unfinished project report documentation. | + | *<font color="black"> Work on unfinished project report documentation.</font> |
− | *Fix the bugs in system testing. | + | *<font color="black"> Fix the bugs in system testing.</font> |
| | | | ||
Line 185: | Line 186: | ||
| 12/19/2017 | | 12/19/2017 | ||
| | | | ||
− | *Perform round 4 of system testing. | + | *<font color="black"> Perform round 4 of system testing.</font> |
− | *Fix the bugs in system testing. | + | *<font color="black"> Fix the bugs in system testing.</font> |
− | *Record a video to demonstrate project working and features. | + | *<font color="black"> Record a video to demonstrate project working and features.</font> |
− | *Complete Documentation of wiki page. | + | *<font color="black"> Complete Documentation of wiki page. </font> |
| | | | ||
Line 196: | Line 197: | ||
| | | | ||
| | | | ||
− | *Ready for Demo. | + | *<font color="black"> Ready for Demo.</font> |
| | | | ||
Revision as of 00:32, 1 November 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 , Team PCB, , Team Android
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.