Difference between revisions of "F15: Undergrads++"
(→Schedule) |
(→Schedule) |
||
| Line 89: | Line 89: | ||
|10/30/2015 | |10/30/2015 | ||
|11/7/2015 | |11/7/2015 | ||
| − | | | + | |Transfer of sensor data via can bus to master |
|...... | |...... | ||
|10/21/2015 | |10/21/2015 | ||
| Line 97: | Line 97: | ||
|10/24/2015 | |10/24/2015 | ||
|10/30/2015 | |10/30/2015 | ||
| − | | | + | |Normalizing sensor data values |
|.... | |.... | ||
|10/30/2015 | |10/30/2015 | ||
| Line 105: | Line 105: | ||
|10/30/2015 | |10/30/2015 | ||
|11/24/2015 | |11/24/2015 | ||
| − | | | + | |Optimizing the code |
|........ | |........ | ||
|11/28/2015 | |11/28/2015 | ||
| Line 115: | Line 115: | ||
|Transfer of sensor data via can bus to master | |Transfer of sensor data via can bus to master | ||
|..... | |..... | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
Revision as of 06:25, 6 October 2015
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.
Project Title
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
- Arlen Eskandari
- Calvin Lai
- Hassan Naveed
- Hector Prado-Guerrero
- Jashan Singh
- Jonathon Hongpananon
- Marvin Flores
- Onyema Ude
- Phil Tran
- Shangming Wong
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# | Date | Task | Actual |
|---|---|---|---|
| 1 | 10/8 | Task list | Completed? Problems Encountered? |
Sensor Controller Team Schedule
| Sl. No | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 10/7/2015 | 10/14/2015 | Researching the Sensors | Complete/incomplete | 10/14/2015 |
| 2 | 10/14/2015 | 10/30/2015 | Connecting the Sensors to the SJOne board and capturing data | ... | 10/14/2015 |
| 3 | 10/30/2015 | 11/7/2015 | Transfer of sensor data via can bus to master | ...... | 10/21/2015 |
| 4 | 10/24/2015 | 10/30/2015 | Normalizing sensor data values | .... | 10/30/2015 |
| 5 | 10/30/2015 | 11/24/2015 | Optimizing the code | ........ | 11/28/2015 |
| 6 | 10/24/2015 | 11/25/2015 | Transfer of sensor data via can bus to master | ..... |
Android/Bluetooth Team Schedule
| Sl. No | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 10/6/2015 | 10/15/2015 | Familiarize ourselves with the Android SDK and Java and Google Maps API | Complete/incomplete | |
| 2 | 10/6/2015 | 10/15/2015 | Have a working menu. | ||
| 3 | 10/10/2015 | 10/18/2015 | Have the phone communicating with the SJOne board using XBee/Zigbee (UART). | ||
| 4 | 10/16/2015 | 11/10/2015 | Relay CAN Bus messages/tasks. | ||
| 5 | 10/18/2015 | 11/15/2015 | Be able to input GPS coordinates and have a working map available. | ||
| 6 | 10/25/2015 | 11/20/2015 | Start and stop commands should be up and running. Test with GPS. | ||
| 7 | 10/20/2015 | 11/27/2015 | Working sensor readings including speed and collisions. | ||
| 8 | 11/15/2015 | 12/01/2015 | Extensive testing of the application and its bridge |
GPS Controller Team Schedule
| Sl. No | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 09/29/2015 | 10/06/2015 | Order Adafruit Compass and GPS and solder header pins | Complete | 10/05/2015 |
| 2 | 10/06/2015 | 10/13/2015 | Connect and get minimum UART connection working and interface compass via I2C | Incomplete | 10/xx/2015 |
| 3 | 10/13/2015 | 10/20/2015 | Design GPS task to parse data and get compass heading info | Incomplete | 10/xx/2015 |
| 4 | 10/20/2015 | 10/27/2015 | Integrate GPS, SJSU board, and CAN rx/tx task | Incomplete | 10/xx/2015 |
| 5 | 10/27/2015 | 11/3/2015 | Test Communication with Master Controller and determine final heading using GPS and compass | Incomplete | 11/xx/2015 |
| 6 | 11/03/2015 | 11/10/2015 | Test and debug (if there are any errors/corner cases) | Incomplete | 11/xx/2015 |
| 7 | 11/10/2015 | 11/17/2015 | Optimize the code and testing for stability and report. | Incomplete | 11/xx/2015 |
Parts List & Cost
| Item# | Part Desciption | Vendor | Part Number | Qty | Cost |
|---|---|---|---|---|---|
| 1 | RC Car | Amazon.com | Traxxas Slash 2WD VXL 58076 | 1 | $339.94 |
| 2 | +++++ | ++++ | +++ | ++ | |
| 3 | CAN Transceiver | Texas Instrument | SN65HVD232D | 5 | Sample |
| 4 | Assembly Components | Amazon.com, Anchor & HSC | PCBs, Mechnical & Electical Components | NA | $++++ |
| 5 | ++++++++++ | ++++++++ | ++++++++++++++ | 1 | $+++ |
| 6 | Sonar sensor | Maxbotix | 3 | $ | |
| 7 | Sonar sensor | Given by Preet | LV-MaxSonar-EZ1 MB1010 | 3 | Free |
| 8 | Adafruit Tripleaxis Accelerometer+Magnetometer(Compass) Board - LSM303 | Adafruit | LSM303 | 1 | $20.97 |
| 9 | LCD Display | 1 | $ | ||
| 10 | 1 | $ |
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:
My Issue #1
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.
